Skip to content
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

Return context error from RetryNotify when done #83

Merged
merged 2 commits into from
Dec 26, 2019
Merged

Conversation

justin-mp
Copy link
Contributor

Previously, when the context used by RetryNotify is done, we return whatever error the last operation returned. The last operation may have run a long time ago (especially when using exponential backoff), so returning last operation error may be very confusing. It makes more sense to return the context's error, which indicates exactly why the context is done.

This fixes #82

Previously, when the context used by RetryNotify is done, we return whatever error the last operation returned.  The last operation may have run a long time ago (especially when using exponential backoff), so returning last operation error may be very confusing.  It makes more sense to return the context's error, which indicates exactly why the context is done.
Return context error from RetryNotify when done
@coveralls
Copy link

Coverage Status

Coverage remained the same at 83.422% when pulling 20d3657 on justin-mp:v3 into 1ff1c09 on cenkalti:v3.

@cenkalti cenkalti added the v4 label Dec 13, 2019
@cenkalti cenkalti merged commit 20d3657 into cenkalti:v3 Dec 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Return Context's error on timeout in RetryNotify
3 participants