I'm using the nbextensions with pleasure for quite some time, and today's conda update has robbed me of them, so I'm sad. ;)
I'm now having these version on my macOS 10.13.6:
(py36) βββ±β±β± conda list nbextensions +8970 19:19 β°ββ
# packages in environment at /Users/klay6683/miniconda3/envs/py36:
#
# Name Version Build Channel
jupyter_contrib_nbextensions 0.5.0 py36_0 conda-forge
jupyter_nbextensions_configurator 0.4.0 py36_0 conda-forge
and the symptom from which I'm inferring that they are inactive are 2-fold:
Here's the weird stuff:
(py36) ββ( 3 ) β±β±β± jn . +8973 19:17 β°ββ
[I 19:17:16.918 NotebookApp] [nb_conda_kernels] enabled, 3 kernels found
[I 19:17:18.607 NotebookApp] Loading IPython parallel extension
[I 19:17:18.690 NotebookApp] [jupyter_nbextensions_configurator] enabled 0.4.0
[I 19:17:18.796 NotebookApp] JupyterLab extension loaded from /Users/klay6683/miniconda3/envs/py36/lib/python3.6/site-packages/jupyterlab
[I 19:17:18.797 NotebookApp] JupyterLab application directory is /Users/klay6683/miniconda3/envs/py36/share/jupyter/lab
[I 19:17:19.331 NotebookApp] Serving notebooks from local directory: /Users/klay6683/Dropbox/src
[I 19:17:19.331 NotebookApp] The Jupyter Notebook is running at:
[I 19:17:19.331 NotebookApp] https://(MacL2938.local or 127.0.0.1):8901/
[I 19:17:19.331 NotebookApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation).
[I 19:17:41.655 NotebookApp] 302 GET / (::1) 2.77ms
and I'm not seeing any other error message? I'm puzzled... any hints how I can debug this?
I have confirmed that this issue goes away when downgrading notebook to 5.6 from 5.7. Should I close here and submit an issue at the jupyter/notebook repo?
Also experienced same issue as @michaelaye after upgrading notebook to ver. 5.7. Downgrading to 5.6 solved this.
Encounter this issue, too. Spent hours on it without any progress. Downgrading solved it.
Seems notebook 5.7 does not include jqueryui anymore. PR #1359 should fix this for the tree-filter extension. This also effects the configurator tab.
Exactly the same issue to me, a waste of almost one day, a terrible experience to me so much. And to be alright by following the solution from all guys above finally, many thanks.
Same thing happened to me. I spent a few hours trying to figure out what was going on, and eventually this issue and doing the downgrade worked for me. I was getting desperate.
Thank you βΊοΈ
yeah, I have a conda config setting on all my installs now that keeps notebook at 5.6 when I do a conda update --all. This is how you can add that to your conda config:
conda config --env --add pinned_packages notebook=5.6
The --env adds this setting ONLY to your currently active environment. That's good because you most likely don't want this to happen everywhere. ;) Just don't forget to regularly check if this issue has been closed and remove the pinning later like so:
conda config --env --remove pinned_packages notebook=5.6
Most helpful comment
I have confirmed that this issue goes away when downgrading notebook to 5.6 from 5.7. Should I close here and submit an issue at the
jupyter/notebookrepo?