-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faraday Timeouts no longer coming through as instance of Graphlient::Errors::FaradayServerError #70
Comments
Possibly also relevant, we internally altered the constructor a bit due to the structure of Faraday::TimeoutError
|
Thanks @BenDrozdoff for reporting this 💜. Feel free to open a PR with your change or I'll try to get to this during holidays. |
NP, looks like the error I was seeing was pretty similar to #68 just with a different Faraday Error class. |
Hi guys, sorry if this caused some pain, that was an involuntary change. Looking at your code, it doesn't seem like you'll need to change anything, but I'd suggest you keep the changes you've done since the changes on our side will come back in Faraday 1.0. |
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
The text was updated successfully, but these errors were encountered: