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

notebook and lab can't open in RTC #390

Open
xiang2002 opened this issue Oct 30, 2024 · 10 comments
Open

notebook and lab can't open in RTC #390

xiang2002 opened this issue Oct 30, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@xiang2002
Copy link

Can't Use RTC in jupyter notebook and jupyterlab

Error

image

image

It only be loading at all time.

Context

  • Operating System and version: Linux Ubuntu 24 for jupyter and open jupyter webpage in my windows PC.
  • Browser : Chrome
  • Jupyter version: jupyterlab:4.2.5,notebook:7.2.2
@xiang2002 xiang2002 added the bug Something isn't working label Oct 30, 2024
@ellisonbg
Copy link

I am seeing the same thing on an upgraded JupyterLab 4.3.0 and jupyter-collaboration 3.0.0.

@ellisonbg
Copy link

Uninstalling jupyter-collaboration resolves the problem.

@ellisonbg
Copy link

Here is a screenshot of the browser Console when I try to create a new notebook with collaboration enabled.

Screenshot 2024-11-05 at 10 41 56 AM

@martinRenou
Copy link
Member

Could you try removing some local .jupyter_ystore.db file, then try again?

@ellisonbg
Copy link

Do you remember which Jupyter path that is under?

@martinRenou
Copy link
Member

It should be local to where you start jupyter lab I believe

@ellisonbg
Copy link

Thanks, confirming for others that deleting the .jupyter_ystore.db in the directory where I started the server does fix the issue. Would be great if jupyter-collaboration can auto-detect when this file needs to be deleted.

@davidbrochart
Copy link
Collaborator

I tried creating a notebook with jupyter-collaboration v2, then upgrading to v3 and opening the notebook again, without issue.
There is some logic to check the store file, that should create a new file in case of version mismatch. We should make sure it works fine.

@ellisonbg
Copy link

Anything else that would cause this?

@davidbrochart
Copy link
Collaborator

Not that I can think of, and without a reproducer it's hard to go further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants