Skip to content

Faraday Timeouts no longer coming through as instance of Graphlient::Errors::FaradayServerError #70

@BenDrozdoff

Description

@BenDrozdoff

Starting in Faraday 0.17.1, the TimeoutError is no longer an instance of Faraday::ClientError, which is caught here as a Graphlient::Errors::FaradayServerError

See this line and this line as the breaking change.

We have some extra error handling logic based on Graphlient::Errors::FaradayServerErrors, so for now we've had to shoehorn in Timeout catching, whereas before they came through in Graphlient.

I haven't been able to dive in enough to figure out exactly what the right solution is, but I'm happy to be part of the discussion

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions