You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
). 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.
The text was updated successfully, but these errors were encountered:
The jupyterlab extension is registering the comm target at notebook creation time (see
jupyter-dash/extensions/jupyterlab/src/index.ts
Line 78 in 351cb7c
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.
The text was updated successfully, but these errors were encountered: