fix potential panic in IsRecoverable #104
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.
The way
unrecoverableError
wraps an error can lead to potential panics. InIsRecoverable
, anunrecoverableError
is passed toerrors.Is
without an embedded error. This is problematic because any error type that implements theIs
interface and expects to be able to callError()
will trigger a panic due to the embedded error beingnil
.To fix this, we can implement
Error()
onunrecoverableError
and handle the case where the embedded error is nil.