retry: distinguish non-retryable errors from timeouts #719
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The WithBackoff function returns a wrapped error with the message "can't retry" both for errors marked as non-retryable by IsRetryable as well as when the context is done. The latter might happen when a positive settings.Timeout is specified, as this results in a wrapped context with a timeout. This behavior resulted in me debugging the IsRetryable function, when just the Timeout has exceeded. To save others from having this experience, I have adapted the messages.
|
#698 addresses the same issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The WithBackoff function returns a wrapped error with the message "can't retry" both for errors marked as non-retryable by IsRetryable as well as when the context is done. The latter might happen when a positive settings.Timeout is specified, as this results in a wrapped context with a timeout.
This behavior resulted in me debugging the IsRetryable function, when just the Timeout has exceeded. To save others from having this experience, I have adapted the messages.