-
Notifications
You must be signed in to change notification settings - Fork 294
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
Interrupting kernel can only be used once #2158
Comments
I encountered the same problem as well. To reproduce the problem: run a cell (which takes for a while) and run this cell again before previous call ends. Now if we click the interrupt kernel, the first call will be interrupted, but the second call starts. At the mean while, the interrupt button greyed out and can not be clicked until I reopen the notebook. |
Thanks for the issue @CYHSM, we'll look into it. I can also reproduce it on Windows. |
To fix, let's not disable the interrupt button if it's clicked before the interrupt actually occurs. |
This is not fixed. The code in the issue still doesn't work. |
For me the interrupt button works, but then two things happen:
|
Doesn't look validated to me. I see the same thing that Rich was seeing where the button is enabled, but the second interrupt never happens and eventually I get a message saying that the interrupt failed and I can restart instead. Tested in raw and jupyter. |
Was previously in may nice to have, so moving to june nice to have. |
Validated, double interrupts allowed now. |
Bug: Notebook Editor, Interactive Window, Editor cells
Steps to cause the bug to occur
Actual behavior
The above loop finishes although kernel was interrupted. This is a special case which I use for interrupting some loops while not interrupting the full process (therefore the KeyboardInterrupt). However, when I use jupyter notebook I can just call interrupt twice when I want to leave the loop. After calling it once in vscode the button for interruption is greyed out and I see a loading bar on top, can't restart kernel in this case and have to close the notebook and reopen it to restart the kernel.
Expected behavior
It would be nice to have the ability to interrupt the kernel until the kernel is actually interrupted. This is probably only an issue if somebody uses "except KeyboardInterrupt" but if it is possible to fix would be nice. Thanks.
Your Jupyter and/or Python environment
Please provide as much info as you readily know
The text was updated successfully, but these errors were encountered: