-
Notifications
You must be signed in to change notification settings - Fork 920
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
Pressing ctrl+\ results in a panic? or segfault? #1647
Comments
Remote command executions such as exec, attach, cp, etc. handle the SIGQUIT (triggered by |
I'm willing to contribute if you could point me to some possible reasons. Right now I'm not sure what's happening, because this doesn't really look like a panic either. I see some synchronization primitives in the log like sync.(*Cond).Wait, so I assume it may be some concurrency issue. ChatGPT suggests a similar conclusion
|
@fira42073 You can try this. |
/triage accepted |
@xyz-li your recommendation above is reasonable and I opened a PR to fix this issue. Thank you. |
What happened:
After running running
kubectl logs -f deploy/gitlab-webservice-default
and then pressing ctl + \
I get the stacktrace and it crashes (see anything else we need to know section)
What you expected to happen:
I'm not sure about the correct behaviour, but it seems like it received the SIGQUIT signal, so probably quit?
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
stacktrace?
Environment:
kubectl version
):gcp cluster
kind setup
Tried this both in working gcp cluster and kind. Same issue.
cat /etc/os-release
):The text was updated successfully, but these errors were encountered: