jupyter lab is stuck when opening a new notebook

[nonZero]

Description

jupyter lab is stuck when opening a new notebook

Reproduce

reproduced in firefox and chrome, including incognito.

does not reproduce with jupyter lab --core-mode !!!

Context

• Operating System and version: arch linux
• Browser and version: latest chrome+firefox
• JupyterLab version: 4.3.1

running in many ways, including uv tool run --python 3.12 --from jupyterlab python -m jupyterlab

Troubleshoot Output

sys.version:
    3.13.0 (main, Oct 16 2024, 03:23:02) [Clang 18.1.8 ]

platform.platform():
    Linux-6.11.9-arch1-1-x86_64-with-glibc2.40

[andrii-i]

Hi @nonZero. Thank you for creating this issue. Could you please advise on the simplest way to reproduce this, if you are seeing this when launching JupyterLab with just jupyter lab? Do you see any browser console errors? Please copy them here if yes.

[felrugo]

I have the same bug. For me it was the RTC: When i open a notebook in Lab then it will open it with an url containig "RTC%3A". If I remove it from the URL and reload the page, the notebook opens normally.

[nonZero]

I have the same bug. For me it was the RTC: When i open a notebook in Lab then it will open it with an url containig "RTC%3A". If I remove it from the URL and reload the page, the notebook opens normally.

Bingo! same here! I think RTC stands for Real Time Collaboation - but I don't think I have anything related installed. @andrii-i is this enough info?

[krassowski]

So this is likely:

• the same as https://github.com/jupyter-server/jupyter_ydoc/issues/293
• fixed by https://github.com/jupyter-server/jupyter_ydoc/pull/294
• released just 15 minutes ago in https://github.com/jupyter-server/jupyter_ydoc/releases/tag/v3.0.2

Can you update jupyter_ydoc locally to 3.0.2 and confirm that this helps?

[felrugo]

Can you update jupyter_ydoc locally to 3.0.2 and confirm that this helps?

For me it does not. It keeps adding RTC in the url and hangs at loading. Also if I replace the RTC part, after some time it stops loading new cells. Only the cell I edited and its neighbours are loaded. If I scroll up it is just empty space...

[nonZero]

Same here.

Is there a way to disable rtc completely as a workaround?

On Tue, Dec 3, 2024, 01:01 felrugo @.***> wrote:

Can you update jupyter_ydoc locally to 3.0.2 and confirm that this helps?

For me it does not. It keeps adding RTC in the url and hangs at loading. Also if I replace the RTC part, after some time it stops loading new cells. Only the cell I edited and its neighbours are loaded. If I scroll up it is just empty space...

— Reply to this email directly, view it on GitHub https://github.com/jupyterlab/jupyterlab/issues/16985#issuecomment-2513157694, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAQHNEIG2PYQO6SZ2ILPUT2DTRGFAVCNFSM6AAAAABSHOTU2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJTGE2TONRZGQ . You are receiving this because you were mentioned.Message ID: @.***>

[krassowski]

Is there a way to disable rtc completely as a workaround?

Yes, but first, can you post the version of jupyter-collaboration that you have installed? Maybe the problem is in incompatible version of jupyter-collaboration? To check run:

pip show jupyter-collaboration

To disable it, assuming latest version and installation via pip, you can uninstall jupyter-collaboration and it's dependencies:

pip uninstall jupyter-collaboration jupyter-docprovider jupyter-server-ydoc jupyter-collaboration-ui

[nonZero]

I believe that the problem is a little harder...

I don't have jupyter-collaboration installed in my virtualenv:

(my_venv) $ pip freeze | grep jupyter
jupyter-events==0.10.0
jupyter-lsp==2.2.5
jupyter-server-mathjax==0.2.6
jupyter_client==8.6.1
jupyter_core==5.7.2
jupyter_server==2.14.0
jupyter_server_fileid==0.9.2
jupyter_server_terminals==0.5.3
jupyterlab==4.3.1
jupyterlab_pygments==0.3.0
jupyterlab_server==2.27.1
jupyterlab_widgets==3.0.10

I am using archlinux and my system' python have:

$ pip freeze | grep jupyter
jupyter-collaboration-ui==1.0.0
jupyter-console==6.6.3
jupyter-docprovider==1.0.0
jupyter-events==0.10.0
jupyter-server-ydoc==1.0.0
jupyter-ydoc==3.0.1
jupyter_client==8.6.3
jupyter_core==5.7.2
jupyter_packaging==0.12.3
jupyter_server==2.14.2
jupyter_server_fileid==0.9.3
jupyter_server_terminals==0.5.3
jupyterlab_pygments==0.3.0

again, --core-mode runs correctly.

a new venv does not run correctly: uv tool run --python 3.12 --from jupyterlab python -m jupyterlab

jupyter from docker runs correctly.

[krassowski]

But you have jupyter-server-ydoc installed:

jupyter-server-ydoc==1.0.0

And you have old version of jupyter-ydoc:

jupyter-ydoc==3.0.1

As per above, the issue should be fixed by 3.0.2.

[nonZero]

Those versions are on my System's python (/usr/bin/python, /usr/lib...). They should not be used or detected by my virualenv's python+jupyter that i am running.

[felrugo]

I am using Manjaro and created a virtualenv (venv) and installed jupyterlab with pip. I did not have jupyter-collaboration installed, but now I installed it directly from pip. Now jupyter seems to be working fine, opening notebook with the RTC url instantly.

I think my problem was that the jupyterlab package did not require jupyter-collaboration therefore the RTC protocoll did not work properly. I dont know how does it work on other platforms, but I think the solution should be that jupyterlab should install the collaboration package as well as I see it is its default opening mode now. Or have it in the docs that one should install the collaboration package as well.

Anyways thank you @krassowski for mentioning the collaboration package. I will test whether the "dissapearing cells" bug solved as well.

[nonZero]

running pip install jupyter-collaboration inside the virtualenv solves the problem.

i.e. in my case jupyterlab inside a venv requires jupyter-collaboration to work properly.

[nonZero]

To easily reproduce:

Runs correctly: uv tool run --from jupyterlab --with jupyter-collaboration jupyter lab

Does not run correctly: uv tool run --from jupyterlab jupyter lab