-
Notifications
You must be signed in to change notification settings - Fork 64
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
Investigate issues with jupyter-contrib-nbextensions for utoronto-configurator #2380
Comments
Jinja2 needs to be pinned for voila but unrelated.
|
Note the extensions list error may be misleading as I don't see a tb above see also Jupyter-contrib/jupyter_nbextensions_configurator#37 |
Upgrading jupyter-nbextensions-configurator from 0.5.1 to 0.7 might fix it, perhaps related to Jupyter-contrib/jupyter_nbextensions_configurator#141? |
Issue still appears with:
|
Actually it functionally works with the upgrade but you have to uncheck "disable configuration for nbextensions without explicit compatibility (they may break your notebook environment, but can be useful to show for nbextension development)" as shown with hide input working on the right. The cli breakage is misleading per above |
Emailed community with testing instructions if that works for them. I tested locally on a clean launch of the image run locally via docker. I did the following in a running
|
Community member was unable to fix in the way I documented. I do not yet have access to the utoronto hub. Going to liase with @yuvipanda to see if we can get a work around for them. |
I tried to see if this was related to the serverapp change (with #2210), but reverting that and deploying to staging had no effect. I'm upgrading nbcontrib (2i2c-org/utoronto-image#48) to see if that helps. |
Aha, with a bit more digging, I'm pretty sure the culprit is Jupyter-contrib/jupyter_nbextensions_configurator#152. I'm going to pin nbclassic<0.5 and see if that fixes things. |
Ref 2i2c-org/infrastructure#2380 Can be removed once Jupyter-contrib/jupyter_nbextensions_configurator#152 is fixed.
Symptoms alleviated by #2411. We need to figure out what the longer term solution there is. |
Following suggestion from Jupyter-contrib/jupyter_nbextensions_configurator#153 that we need to explicilty enable the configurator. nbclassic also has hit 1.0, which might help. Ref 2i2c-org/infrastructure#2380
This is upstream, closing now. |
Brings in 2i2c-org/utoronto-image#58, so we no longer have to use the older notebook server. Fixes 2i2c-org#2380 Ref 2i2c-org#2729
Brings in 2i2c-org/utoronto-image#58, so we no longer have to use the older notebook server. Fixes 2i2c-org#2380 Ref 2i2c-org#2729
2i2c-org/utoronto-image#58 actually fixes this, #3550 rolls it out to just the staging utoronto hub. It can be rolled out to prod on Jan 9. |
I think this landed into production on Jan 9th, ref: #3598. |
Context
via https://2i2c.freshdesk.com/a/tickets/554
jupyter-contrib-nbextensions is
installed. I'll note that running jupyter nbextension list shows
"nbextensions_configurator/config_menu/main", but there are "problems
found" with that extension.
Proposal
No response
Updates and actions
No response
The text was updated successfully, but these errors were encountered: