-
Notifications
You must be signed in to change notification settings - Fork 305
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
Why can't the terminal be interrupted? #668
Comments
I just tried with Jupyter Lab, and |
The bash process also cannot be killed when kill -1 <bash_pid> |
But I do the same by connecting to the container via ssh and can interrupt the process with ctrl+c |
yeah, It's so confusing, I can use it on my mac and it can be interrupted. what information do I need to provide? |
|
os: pip freeze
|
Thanks, what's your Python version? |
Execute the following command, the subprocess of bash cannot be killed
|
Python 3.6.13 |
|
thank you for your reply, I will close this issue |
Can we re-open this issue? I'm experiencing this intermittently as well. After the SIGINT fails to kill the server process, I sometimes see the following output printed to the terminal. I think this is highly relevant to this issue:
|
I am also experiencing this as of late (couldn't kill the server using SIGINT). |
Does it happen when enabling collaborative mode? I can see a possibility for it to happen because of asyncio tasks not being cancelled on exit (in jupyter-collaboration and ypy-websocket). |
I managed to reproduce the issue. For some reason, whenever I start |
Thanks for the feedback @dlqqq. Probably |
When I execute
tail -f jupyter.log
in terminal, it cannot be interrupted by ctrl+cThe text was updated successfully, but these errors were encountered: