-
Notifications
You must be signed in to change notification settings - Fork 293
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
IPyWidgets do not work when connecting to existing remote Jupyter Kernels #8179
Comments
Also per #8085, I can confirm that on v2021.10.1001414422 of the Jupyter extension |
@zpincus I've tested ipywidgets when connecting to remote kernels in the past 2 releases & I coulnd't get it to work. However I've managed to fix this fairly easily (PR submitted). |
Thanks a ton! This is a big improvement. FWIW, as far as I recall |
Fixed and it will be in the next insiders, we'll (team) discuss next week during our triage meeting whether to ship this as part of the recovery release or not (since its not a regression, its unlikely to ship as part of the recovery release). Closing as this issue has been resolved, |
Testing steps:
import ipywidgets
ipywidgets.IntSlider() |
Reported by https://github.com/zpincus
#8085 (comment)
Unfortunately, even with the new changes in Jupyter extension version 2021.10.100, this bug in fact does still affect reconnecting to existing sessions on a remote server.
That is, connecting to a new kernel (and creating a session on the remote server) now no longer breaks ipywidgets, but when re-connecting to an existing session, widgets are still broken.
The easiest steps to reproduce this are:
NameError
).NameError
, but no slider either.If you then go to the kernel picker and create a kernel session, you can run both cells and the slider reappears. But again connecting back to the existing session, the slider will not appear and ipywidgets remains broken.
@IanMatthewHuff would you prefer I create a new issue for this part of the bug, or just keep it all in this issue?
The text was updated successfully, but these errors were encountered: