-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
util/stop: fix span use when recovering from a panic #83290
Conversation
When recovering from a panic, the stopper was first finishing the tracing span and then using it to log the panic. This was a use-after-finish. It was not caught by the unit test because the test was short-circuiting the logging part; I've improved the test so that it would have caught it. Release note: None
The goroutine dealing with reading from a pgwire connection was logging panics, but that was redundant with what the Stopper was about to also do. Release note: None
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.
Reviewed 2 of 2 files at r1, 2 of 2 files at r2, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @andreimatei)
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.
bors r+
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @andreimatei)
This PR was included in a batch that was canceled, it will be automatically retried |
Build failed (retrying...): |
Build succeeded: |
When recovering from a panic, the stopper was first finishing the
tracing span and then using it to log the panic. This was a
use-after-finish. It was not caught by the unit test because the test
was short-circuiting the logging part; I've improved the test so that it
would have caught it.
Release note: None