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

disconnect SSH caused kernel being killed #10948

Closed
ydmykr opened this issue Jul 27, 2022 · 1 comment
Closed

disconnect SSH caused kernel being killed #10948

ydmykr opened this issue Jul 27, 2022 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged

Comments

@ydmykr
Copy link

ydmykr commented Jul 27, 2022

After Using SSH Remote connection, disconnecting will kill the kernel.

How can I disconnect, then reconnect to a vscode dev container without killing the ipynb kernel within my workspace?

@ydmykr ydmykr added the bug Issue identified by VS Code Team member as probable bug label Jul 27, 2022
@github-actions github-actions bot added the triage-needed Issue needs to be triaged label Jul 27, 2022
@rchiodo
Copy link
Contributor

rchiodo commented Jul 27, 2022

Thanks for the issue.

The only way for a kernel to survive the VS code extension host dying (the process where our extension runs) is to use a jupyter server instead.

See this issue for a discussion on using the 'remote' server to control your kernel lifetime.

@rchiodo rchiodo closed this as completed Jul 27, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 28, 2023
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 triage-needed Issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants