KeyError: '@jupyterlab/apputils' when installing voyager?

[alston19]

Hi there, I failed to install jupyterlab_voyager running jupyter labextension install jupyterlab_voyager as showed in README.md. It shows 'KeyError: @jupyterlab/apputils'`.

I can install other extensions like toc and go-to-definition. How can I fix it? THANKS.

[playermanny2]

@alston19 which version of jupyterlab are you using?

[alston19]

@alston19 which version of jupyterlab are you using?

I'm using jupyterlab 1.1.0a1. I first use old version but failed to build jupyterlab, so I upgrade it to v1.1.0a1 according to community. other package versions:

• npm: 4.6.1
• node: v11.15.0 (first v12.7.0, but erros happened)
• jupyter: 4.4.0

[playermanny2]

@alston19 we've updated the package 8/14/2019 so far, this has been tested with jupyterlab 1.0.4

Could you try it with jupyterlab 1.0.4, now the alpha?

Also posting the stacktrace would help if the error proceeds

[alston19]

@alston19 we've updated the package 8/14/2019 so far, this has been tested with jupyterlab 1.0.4

Could you try it with jupyterlab 1.0.4, now the alpha?

Also posting the stacktrace would help if the error proceeds

It seems my jupyterlab also broke down. I'll try it with 1.0.4 and will post the error log later. Thanks a lot!

[dfdf]

Facing the same issue with the new release of Jupyter Lab, version at 1.1.0

[playermanny2]

@dfdf Hi, this extension has only been tested with jupyterlab 1.0.4 -- please use with this version, as we may have to perform updates to use with 1.1.0

[JamesSample]

I'm running into this issue when trying to install Voyager using Docker and JupyterLab 1.0.4. For example, the following Docker file has a broken sidebar for me:

# datascience-notebook image with JupyterLab 1.0.4
ARG BASE_CONTAINER=jupyter/datascience-notebook:2ce7c06a61a1
FROM $BASE_CONTAINER

RUN jupyter labextension install jupyterlab_voyager --no-build && \
    jupyter lab build --dev-build=False && \
    npm cache clean --force && \
    rm -rf $CONDA_DIR/share/jupyter/lab/staging && \
    rm -rf /home/$NB_USER/.cache/yarn && \
    rm -rf /home/$NB_USER/.node-gyp && \
    fix-permissions $CONDA_DIR && \
    fix-permissions /home/$NB_USER

I can fix the sidebar problem by upgrading to 1.1.1, but then the Voyager installation fails. Originally, I was getting KeyError: @jupyterlab/apputils, but now (a few days later) I just see jupyter labextension install [...] returned a non-zero code: 1.

How are folks currently managing to install Voyager, given it's not yet compatible with JupyterLab 1.1.1, but lower version numbers have the problem with the sidebar?

Thanks!

[playermanny2]

@JamesSample very weird, I just tried with a Dockerfile created directly from your above code and it worked fine. I would assume now it may be more to your issue, is that all the code in your Dockerfile?

[JamesSample]

@playermanny2. Thanks for your reply!

Hmm, that is weird.

Yes - that's the entire Docker file; my actual Docker file is more complicated, but I stripped it down to the minimal example here and I still have the same problem. It must be something to do with my system, as you suggest. I'll update here if I figure it out.

[playermanny2]

@JamesSample I would try pruning your docker system, and also trying with the minimal or base jupyter image -- when you say broken sidebar, what are you referring to?

[JamesSample]

@playermanny2 Thanks!

I've run docker system prune and have also tried with the minimal-notebook image, but with the same result. I tried upgrading Docker too, but no change :-(

If I build the Dockerfile above and then launch JupyterLab using

docker run -ti --rm -p 8888:8888 -v ${PWD}:/home/jovyan/work test start.sh jupyter lab

I see the following

Other extensions produce exactly the same problem, so this isn't specifically a Voyager issue: anything involving jupyter lab build seems to break my installation (unless I'm using JupyterLab 1.1.1). I posted here because you've obviously got it working with 1.0.4 and I wondered how, but if it just works for you I guess it's a problem with my system (although I'm not the only one).

Thanks for your work on the Voyager2 extension - it's a great tool and I'll miss it until I get it working again!

[playermanny2]

@JamesSample Ah, sorry I misread your original issue. I thought you meant the Docker image would not build at all. I also saw the sidebar issue after running the container...i'm not sure why this could be occuring. when i originally tested it these issues weren't occuring...I can only assume now the best option would be to potentially downgrade to 1.0.2 (as it seems from the referenced issue that could fix it) and in the meantime we will work on upgrading for jupyter 1.1.1

I currently have a working version using https://hub.docker.com/r/jupyter/all-spark-notebook but i haven't rebuilt the image for a few weeks...