-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
🐛 Fix TerminalError(nil).Error() panic #2438
🐛 Fix TerminalError(nil).Error() panic #2438
Conversation
|
Welcome @sheidkamp! |
Hi @sheidkamp. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
a993454
to
e3ad494
Compare
if te.err == nil { | ||
return "nil terminal error" | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a common pattern? We're at this point creating an error with a nil cause/inner error which might throw off the reconciliation loop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only see it used here:
if errors.Is(err, reconcile.TerminalError(nil)) { |
which doesn't totally make sense because the previous line checks for
err==nil
(<- strikethrough because checking for err==nil
does not mean that the unwrapped error is not nil)
An alternate solution would be to modify the controller to create that error with a non-nil value (empty string?) and maybe add protection in the TerminalError() function to not allow nil values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The nil terminal error there is only used for the errors.Is
comparison, in that context, the Error()
method will never be called.
It isn't really expected to construct a terminal error with a nil inner error when returning it, as that means logging will not be able to tell you what the issue was. When did you run into this panicing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We run into this error when using the Eris error handling library. Example here:
https://go.dev/play/p/4N0EmuNcPHJ
errors.Is
calls the 1st argument's Is
method here: https://cs.opensource.google/go/go/+/master:src/errors/wrap.go;l=54?q=wrap.go&ss=go%2Fgo
And then Eris' Is
function does call target.Error()
https://github.com/rotisserie/eris/blob/d0c56b6433ca96eedf3c9482ec51456aa80dd772/eris.go#L212
leading to the panic.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alvaroaleman, sheidkamp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Fixes #2430 by checking it
err
is nil before callingError()
on it.