Skip to content

find better solution than sys.exit for 502 error #699

Description

@Marmingen

Description

When we send a get req to MELOS (will be the same with UPRIGHT) and a 502 Bad Gateway error is returned, sys.exit(1) is called. The membership information is cached in our local dbs, thus this could in the short term be circumvented.

Specifically, add a try-except in melos_client.py

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions