Skip to content

Better error handling #40

@longears

Description

@longears

There are a lot of different exceptions that can come from the resuests library and the underlying sockets code.

Should those all be caught by our library and converted into a simpler set of exceptions?

Consider also some sanity checking of JSON going into and out of Tent.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions