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.

Sign up for GitHub

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

Jump to bottom

Figure out relaunching dead kernels #1

Open
takluyver opened this issue Apr 24, 2018 · 1 comment
Open

Figure out relaunching dead kernels #1

takluyver opened this issue Apr 24, 2018 · 1 comment

Comments

@takluyver
Copy link
Owner

Leaving a note for myself so I don't forget about it.
@takluyver
Copy link
Owner Author

The interface in jupyter_kernel_mgmt.restarter seems more or less right for notebook, but there are a couple of bits missing:

  • event to fire after a successful restart
    • Do we then still need the even before restarting, or is that superfluous?
  • a way to get the new connection info after a new kernel is started
  • should callbacks have parameters?
  • make a decision on KernelManager.relaunch() - I'm inclined to do away with this and decide that any restart is done by creating a completely new kernel and announcing that it replaces the old one. That's one fewer code path to go wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@takluyver