-
Notifications
You must be signed in to change notification settings - Fork 118
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
remove retry logic #100
remove retry logic #100
Conversation
@drbrain does this look good ? ... if ye I'll start fixing the tests |
@drbrain looks like the right direction ? |
@drbrain looks like the right direction ? (I still need to change all the tests if yes) |
added tests @tenderlove are you able to merge since @drbrain seems to ignore this PR ? :( |
releasing this as net-http-persistent-retry so I can use it in my other projects and can declare an actual dependency, will yank if this ever gets merged 🤷♂ |
…implified (instead of `Faraday::ConnectionFailed`) In v3 net-http-persistent rescue a lot of exceptions and retries them or re-raises them as Net::HTTP::Persistent::Error which is complicated and unnecessary. When drbrain/net-http-persistent#100 gets merged (or when using [net-http-persistent-retry](https://github.com/grosser/net-http-persistent) which is a fork of net-http-persistent with that PR applied) the error wrapping/retry goes away and it will start raising "normal" errors like `Net::OpenTimeout` which is a `Timeout::Error`. /cc @drbrain @mislav @iMacTia
Merged, see log above. |
awesome, thx! :D |
The net-http-persistent gem removed the #retry_change_requests adapter configuration with drbrain/net-http-persistent#100 in v4.0.0.
Net::HTTP::Persistent removed `#retry_change_requests` in v4.0.0 and later, so these tests fail if we've pulled in a more recent version than that. Related to drbrain/net-http-persistent#100
Net::HTTP::Persistent removed `#retry_change_requests` in v4.0.0 and later, so these tests fail if we've pulled in a more recent version than that. Related to drbrain/net-http-persistent#100
fixes #37
fixes #89
@tenderlove @timanovsky @drbrain
not sure if this breaks RFC 2616 but idk what part of the readme it was referring to when it mentioned the RFC, I'd assume the closing the connection which is still there