Skip to content

Add server error and 429 handling in fetch scripts #103

@itrujnara

Description

@itrujnara

Description of the bug

As it stands, fetch scripts and the underlying utils are prepared to handle timeouts and 404 errors. They should also be ready to handle server errors (by sending a retry signal, i.e., exit code 10), as well as 429 errors (method TBD).

Command used and terminal output

Relevant files

No response

System information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions