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

Failed to load the jupyterlab-git server extension #1333

Open
psychemedia opened this issue Jun 10, 2024 · 7 comments
Open

Failed to load the jupyterlab-git server extension #1333

psychemedia opened this issue Jun 10, 2024 · 7 comments
Labels

Comments

@psychemedia
Copy link

Trying to run JupyterLab with the latest package in a clean Docker build, I get:

Failed to load the jupyterlab-git server extension
The versions of the JupyterLab Git server frontend and backend do not match. The @jupyterlab/git frontend extension has version: 0.50.0 while the python package has version 0.50.1. Please install identical version of jupyterlab-git Python package and the @jupyterlab/git extension. Try running: pip install --upgrade jupyterlab-git
image
@jab
Copy link

jab commented Jun 30, 2024

Just tried installing this extension for the first time, in a freshly-installed JupyterHub instance, and immediately hit this issue. Are you able to reproduce this @Zsailer et al.?

@akashkroy
Copy link

I had the same issue in jupyterhub. Restarted the server resolved it.

@jab
Copy link

jab commented Jul 4, 2024

Restarting did not resolve the issue for me.

@fcollonval
Copy link
Member

i don't know if this was the reason. But I saw that version 0.50.1 failed to be published on conda-forge. It is done now. Does that solve your issue?

@jab
Copy link

jab commented Jul 8, 2024

No, that didn’t fix this issue. It should be easy to check that this is still broken. Just try installing jupyterlab-git in a fresh jupyterlab instance (eg using the Extensions tab in the UI) then observe that every time you load the UI you get the error “Failed to load the jupyterlab-git server extension”.

@krassowski
Copy link
Member

@jab I deployed hundreds of JupyterLab servers and did not encounter this issue. Your problem may be that you are installing the extension too late, this is after the single user server has started. Alternatively, you may be running the legacy notebook server instead of jupyter-server. Running jupyter server extension list, pasting startup logs from the single user server and the JupyterHub configuration may help to give us better picture here.

@xiongjiamu
Copy link

xiongjiamu commented Jul 15, 2024

@krassowski
this is my jupyter server extension list outpu:

(base) jovyan@bc4396815f67:~$ jupyter server extension list
Config dir: /home/jovyan/.jupyter

Config dir: /opt/conda/etc/jupyter
    jupyter_lsp enabled
    - Validating jupyter_lsp...
      jupyter_lsp 2.2.5 OK
    jupyter_server_mathjax enabled
    - Validating jupyter_server_mathjax...
      jupyter_server_mathjax  OK
    jupyter_server_terminals enabled
    - Validating jupyter_server_terminals...
      jupyter_server_terminals 0.5.3 OK
    jupyterlab enabled
    - Validating jupyterlab...
      jupyterlab 4.2.3 OK
    jupyterlab_git enabled
    - Validating jupyterlab_git...
      jupyterlab_git 0.50.1 OK
    nbclassic enabled
    - Validating nbclassic...
A `_jupyter_server_extension_points` function was not found in nbclassic. Instead, a `_jupyter_server_extension_paths` function was found and will be used for now. This function name will be deprecated in future releases of Jupyter Server.
      nbclassic 1.1.0 OK
    nbdime enabled
    - Validating nbdime...
      nbdime 4.0.1 OK
    notebook enabled
    - Validating notebook...
      notebook 7.2.1 OK
    notebook_shim enabled
    - Validating notebook_shim...
      notebook_shim  OK

Config dir: /usr/local/etc/jupyter

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

No branches or pull requests

6 participants