We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Elixir & Erlang versions (elixir --version): Erlang/OTP 23, Interactive Elixir (1.10.4)
ExAws version mix deps |grep ex_aws2.0.2
mix deps |grep ex_aws
HTTP client version. IE for hackney do mix deps | grep hackney 1.16
mix deps | grep hackney
In case of SQS unavailability retry cycle is executed one iteration less than expected.
It seems strict ">" should be used in attempt_again? in request.ex as "attempt" starts from 1.
def attempt_again?(attempt, reason, config) do if attempt >= config[:retries][:max_attempts] do
So retry cycle is executed (max_attempts - 1) times.
Retry cycle should be executed max_attempts times.
The text was updated successfully, but these errors were encountered:
I may be wrong, but that's not how I read it:
attempt
1
request.ex:20
attempt_again?
max_attempts
2
else
Sorry, something went wrong.
No branches or pull requests
Environment
Elixir & Erlang versions (elixir --version): Erlang/OTP 23, Interactive Elixir (1.10.4)
ExAws version
mix deps |grep ex_aws
2.0.2HTTP client version. IE for hackney do
mix deps | grep hackney
1.16Current behavior
In case of SQS unavailability retry cycle is executed one iteration less than expected.
It seems strict ">" should be used in attempt_again? in request.ex as "attempt" starts from 1.
So retry cycle is executed (max_attempts - 1) times.
Expected behavior
Retry cycle should be executed max_attempts times.
The text was updated successfully, but these errors were encountered: