-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
apiserver: forward panic in WithTimeout filter #68001
apiserver: forward panic in WithTimeout filter #68001
Conversation
/retest |
tw := newTimeoutWriter(w) | ||
go func() { | ||
defer func() { | ||
result <- recover() |
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.
so easy to start a gofunc, so easy to forget to recover panics in it.
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.
Now go through all go funcs in Kube and prepare for new grey hair.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, sttts 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 |
/retest |
/hold Checking whether the test failures are real. |
Seeing the same flakes in #64149, totally unrelated PR. /hold cancel |
/retest Review the full test history for this PR. Silence the bot with an |
Automatic merge from submit-queue (batch tested with PRs 66577, 67948, 68001, 67982). If you want to cherry-pick this change to another branch, please follow the instructions here: https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md. |
/assign @caesarxuchao |
…release-1.11 Automated cherry pick of #68001: apiserver: forward panic in WithTimeout filter
while stopping the apiserver crashes (\o/) this also loses stack information from the propagated panic (/o). Will open a follow-up |
Without this PR a panic in a HTTP handler will not be caught in the Go routine started by the timeout filter. Uncaught panics terminate the process.
This is a strong condidate to be backported to 1.11, 1.10 and 1.9.