Skip to content

handle exceptions when using already deployed functions on DiSARM OpenFaas #9

@onlyjsmith

Description

@onlyjsmith

@ric70x7 could you try out a version of the disarm-gears code with e.g. a completely wrong URL included, and see what happens in one of the functions that uses it? (e.g. fn-prev-predictor). If it's clear in the return to the user running the fn-prevalence-predictor (and ideally, the logs) that there was an error in another function, then think we're ok. If the error message is blank, or ambiguous, we might need to add some more exception handling (try:... except:...) around network requests.

Relates to #8

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions