Ensure nil is not passed to RetryError helpers #14104
Merged
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.
V2 of the SDK now errors if
nil
is passed to either of theRetryError
helpers, this is to avoid subtle logical bugs. Certain patterns which naively returnresource.NonRetryableError(err)
whenerr == nil
as a convenience to bubbling up nil should be avoided in favor of explicit error checking. It's possible this PR fixes some bugs in the wild 🤷♂️, main goal is to remove noise from V2 SDK acceptance tests.Community Note
Relates OR Closes #0000
Release note for CHANGELOG:
Output from acceptance testing: