notebook and lab can't open in RTC

[xiang2002]

Can't Use RTC in jupyter notebook and jupyterlab

Error

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

[ellisonbg]

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

[ellisonbg]

Uninstalling jupyter-collaboration resolves the problem.

[ellisonbg]

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

[martinRenou]

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

[ellisonbg]

Do you remember which Jupyter path that is under?

[martinRenou]

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

[ellisonbg]

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]

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]

Anything else that would cause this?

[davidbrochart]

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

[brichet]

I can reproduce it when updating a package that depends on jupyterlab_collaboration 3 instead of 2 before.
The jupyter_server_ydoc server extension is not installed.

For example with jupyterlab_chat on main (depends on jupyter_collaboration<3), the server extensions are:

    jupyter_lsp enabled
    - Validating jupyter_lsp...
      jupyter_lsp 2.2.5 OK
    jupyter_collaboration enabled
    - Validating jupyter_collaboration...
      jupyter_collaboration 2.1.4 OK
    jupyter_server_fileid enabled
    - Validating jupyter_server_fileid...
      jupyter_server_fileid 0.9.3 OK
    jupyter_server_terminals enabled
    - Validating jupyter_server_terminals...
      jupyter_server_terminals 0.5.3 OK
    jupyterlab enabled
    - Validating jupyterlab...
Extension package jupyterlab took 0.1392s to import
      jupyterlab 4.2.5 OK
    jupyterlab_chat enabled
    - Validating jupyterlab_chat...
      jupyterlab_chat 0.6.2 OK
    notebook_shim enabled
    - Validating notebook_shim...
      notebook_shim  OK

Installing again the package from that PR (depends on jupyter_collaboration>=3) leads to:

     jupyter_lsp enabled
    - Validating jupyter_lsp...
      jupyter_lsp 2.2.5 OK
    jupyter_server_fileid enabled
    - Validating jupyter_server_fileid...
      jupyter_server_fileid 0.9.3 OK
    jupyter_server_terminals enabled
    - Validating jupyter_server_terminals...
      jupyter_server_terminals 0.5.3 OK
    jupyterlab enabled
    - Validating jupyterlab...
Extension package jupyterlab took 0.1640s to import
      jupyterlab 4.2.5 OK
    jupyterlab_chat enabled
    - Validating jupyterlab_chat...
      jupyterlab_chat 0.6.0 OK
    notebook_shim enabled
    - Validating notebook_shim...
      notebook_shim  OK

The jupyter_server_ydoc server extension is not installed, but the package is.

This can be tried running ./scripts/dev_install.sh from the sources of jupyter-chat.

Of note, the installation works well when starting from a new environment.

[ellisonbg]

Thanks for reproducing this @brichet !

[andrii-i]

I can reliably and easily reproduce this problem by updating from jupyterlab-chat version that uses jupyter-collaboration v2 to one that uses jupyter-collaboration v3 as so:

1. Create new conda environment
2. Run pip install jupyterlab-chat==0.6.2 (depends on jupyter-collaboration<3, v2.1.5 in my case)
3. Create a new folder and run jupyterlab in it, create a chat which would create a chat file
4. Run pip install jupyterlab-chat==0.7.1(depends on jupyter-collaboration>3, v3.1.0 in my case)
5. Attempt to open previously created chat file in jupyterlab and see spinning circle

Next I looked into .jupyter_ystore.db and PRAGMA user_version is still 2 so old .jupyter_ystore.db is not getting detected as old and moved by db check logic in _init_db logic function as it is supposed (referenced in #414 (comment))

@davidbrochart, could you please look into this comment and why _init_db is not detecting db as old in this reproduction path?

Theory of mine is that in version check codemove_db flag is set to true only if pragma user_version doesn't match self.version . So if one of them is not set correctly or if they don't match (for example, db schema is different or pragma was not set or self.version is not set), db would not be moved. Instead create_db logic would attempt to create an already existing table, error out, and rollback the transaction invalidating all following transactions including the one that is supposed to set version to 3.

SQLite commands that I used / are used in `_init_db` function:

1. Open .jupyter_ystore.db file in terminal

sqlite3 .jupyter_ystore.db

2. Check existence of yupdates table

SELECT count(name)
FROM sqlite_master
WHERE type='table'
  AND name='yupdates';

3. Check pragma user_version

PRAGMA user_version;