Skip to content
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.

Switching kernel breaks the extensions #64

Open
dpinte opened this issue Jul 29, 2021 · 0 comments
Open

Switching kernel breaks the extensions #64

dpinte opened this issue Jul 29, 2021 · 0 comments

Comments

@dpinte
Copy link

dpinte commented Jul 29, 2021

The jupyterlab extension is registering the comm target at notebook creation time (see

notebooks.widgetAdded.connect((sender, nbPanel: NotebookPanel) => {
). This means that changing the kernel will not work. In practice all calls to JupyterDash.infer_jupyter_proxy_config() will fail after the kernel is changed (for a good reason).

A potential solution would be to listen to the ISessionContext.kernelChanged signal and register the comm target against the updated kernel.

I have only tested it with Jupyterlab but I suspect the nbextension has the same problem.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant