Skip to content
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

"Kernel died unexpectedly" after shutting down a kernel and opening a notebook again #1185

Closed
jtpio opened this issue Oct 2, 2023 · 3 comments · Fixed by #1186
Closed

"Kernel died unexpectedly" after shutting down a kernel and opening a notebook again #1185

jtpio opened this issue Oct 2, 2023 · 3 comments · Fixed by #1186
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jtpio
Copy link
Member

jtpio commented Oct 2, 2023

Follow-up to the JupyterLab 4 / Notebook 7 update: #1019

The following steps trigger a "Kernel died unexpectedly" error dialog:

  • open an existing notebook
  • shut down the associated kernel via the running panel
  • close the notebook
  • open the notebook again
kernel-shutdown-open-error.mp4
@jtpio jtpio added the bug Something isn't working label Oct 2, 2023
@jtpio jtpio added this to the 0.2.0 milestone Oct 2, 2023
@jtpio
Copy link
Member Author

jtpio commented Oct 2, 2023

This could be related to the change in jupyterlab/jupyterlab#13792 which is using the kernel manager, while it was using the sessions API before:

image

@jtpio jtpio self-assigned this Oct 2, 2023
@jtpio
Copy link
Member Author

jtpio commented Oct 3, 2023

The running panel is also not accurately indicating when the same kernel is used in both a notebook and a console:

image

@jtpio
Copy link
Member Author

jtpio commented Oct 3, 2023

The running panel is also not accurately indicating when the same kernel is used in both a notebook and a console:

Ah actually this might be an issue upstream in JupyterLab:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant