Skip to content
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

extensions suddenly vanished #1356

Open
michaelaye opened this issue Sep 27, 2018 · 7 comments
Open

extensions suddenly vanished #1356

michaelaye opened this issue Sep 27, 2018 · 7 comments

Comments

@michaelaye
Copy link

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:

  1. I usually have the dashboard directory listing FILTER active, that's not there anymore
  2. As I have the configurator package installed, giving me a notebook tab where I can configure the extensions, that's gone as well.

Here's the weird stuff:

  1. the configurator notes that it is loaded, as per jupyter log:
(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?

@michaelaye
Copy link
Author

michaelaye commented Sep 27, 2018

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?

@SteliosStefanatos
Copy link

Also experienced same issue as @michaelaye after upgrading notebook to ver. 5.7. Downgrading to 5.6 solved this.

@astroboylrx
Copy link

Encounter this issue, too. Spent hours on it without any progress. Downgrading solved it.

@juhasch
Copy link
Member

juhasch commented Oct 13, 2018

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.

@hepingtao
Copy link

hepingtao commented Oct 25, 2018

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.

@iipr
Copy link

iipr commented Oct 25, 2018

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 ☺️

@michaelaye
Copy link
Author

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

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

No branches or pull requests

6 participants