-
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
Interrupt/Restart Slow or Not Working #7867
Labels
bug
Issue identified by VS Code Team member as probable bug
notebook-execution
Kernels issues (start/restart/switch/execution, install ipykernel)
Comments
My understanding is that sometimes the kernel cannot be restarted or interrupted because it's executing code outside of the Python kernel proper. In these cases, the external code has to finish running before an interrupt will be honored. Wouldn't this problem also happen in Jupyter Lab and Jupyter Notebook? |
Interrupt is handled by the jupyter extension |
greazer
added
notebook-execution
Kernels issues (start/restart/switch/execution, install ipykernel)
and removed
needs-triage
labels
Oct 11, 2021
DonJayamanne
changed the title
Notebooks - Interrupt/Restart Slow or Not Working
Interrupt/Restart Slow or Not Working
Oct 12, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bug
Issue identified by VS Code Team member as probable bug
notebook-execution
Kernels issues (start/restart/switch/execution, install ipykernel)
I have a hunch that interrupt not working is coming from the cell level based on previous feedback and my own experience as well. The cell level interrupt sometimes just doesn't work and requires restarting the entire kernel.
The text was updated successfully, but these errors were encountered: