Persistent Jupyter Kernels - Restore/Re-connect to an existing local/remote kernel (do not shutdown kernel upon closing/reloading vscode/vscode.dev)

# Problem ## Local * User starts a notebook, the kernel is now running on the local machine * Assume the computer goes to sleep, * After a while if we go back into the notebook, the Notebook is unable to re-connect to the same kernel (kernel state is lost) * Similarly if user re-loads VS Code, the notebook is unable to re-connect to the same kernel (kernel state is lost) * Similarly if a user is using Remote SSH, and connection is reset and user re-connects and opens the same notebook, then the user is unable to re-connect to the same kernel (kernel state is lost) ## Remote * User opens a notebook and runs a cell against a remote kernel * Similarly if user re-loads VS Code (or vscode.dev), the notebook is unable to re-connect to the same kernel (kernel state is lost) **Investigation Running Server & JupyterLab API for extensibility** **Goals:** * Long running kernels * User can open a notebook with a cell thats still running & see the output being generated * Same as User can open notebooks related to kernels that are still running. * Extensibility for extension authors This is a by-product of the long running kernels (i.e. you get this for free - almost) **Planned (related) Prototypes** * Long running kernels Solve problems related to kernel/session being lost due to : * VS Code Shutdown * VS Code Restart * Computer sleeping * SSH connection issues * AML Compute will benefit * By product of extensiblity * Julia Widgets (i might end up do

Posted by DonJayamanne on Nov 20, 2020, 10:26 PM

Tags

• github (Sysadmin)

Related issues

• Custom games stuck on "finding server" for all european servers
• Feature request: add ACP (Agent Client Protocol) stdio JSON-RPC mode
• Forza Horizon 6 (2483190)
• Turn off integrated browser for default
• Weekly updates are too frequent
• [BUG] Max 20x plan: 100% usage after 2 hours of light work (5 commits, no agents)