Error "Unexpected type: notebook" when creating new notebook from launcher

I am running JupyterHub on k8s and JupyterLab and recently have gotten this error when creating new notebooks from the Launcher. Here are some relevant library versions I have installed:

jupyter-ai                2.28.3             pyhd8ed1ab_0    conda-forge
jupyter-ai-magics         2.28.3             pyhd8ed1ab_0    conda-forge
jupyter-lsp               2.2.5              pyhd8ed1ab_0    conda-forge
jupyter-marimo-proxy      0.0.4                    pypi_0    pypi
jupyter-resource-usage    1.1.0              pyhd8ed1ab_0    conda-forge
jupyter-server-proxy      4.4.0                    pypi_0    pypi
jupyter_client            8.6.3              pyhd8ed1ab_0    conda-forge
jupyter_core              5.7.2              pyh31011fe_1    conda-forge
jupyter_events            0.10.0             pyhd8ed1ab_0    conda-forge
jupyter_server            2.14.2             pyhd8ed1ab_0    conda-forge
jupyter_server_terminals  0.5.3              pyhd8ed1ab_0    conda-forge
jupyterhub                5.2.1              pyh31011fe_0    conda-forge
jupyterhub-base           5.2.1              pyh31011fe_0    conda-forge
jupyterlab                4.3.2              pyhd8ed1ab_0    conda-forge
jupyterlab-lsp            5.1.0              pyhd8ed1ab_3    conda-forge
jupyterlab-s3-browser     0.12.0             pyhd8ed1ab_1    conda-forge
jupyterlab_pygments       0.3.0              pyhd8ed1ab_1    conda-forge
notebook                  7.3.1              pyhd8ed1ab_0    conda-forge
notebook-shim             0.2.4              pyhd8ed1ab_0    conda-forge

I don’t see any errors in the user pod logs. Any ideas where to start looking/debugging?

An interesting observation. If I open an existing .ipynb notebook or create a new notebook by right clicking in the File Browser and selecting “New Notebook”, the notebooks open/create just fine and the Launcher starts working again afterwards.

Refreshing the browser and using the Launcher results in the same error.

I bisected the error as being introduced from the jupyter-s3-browser extension. Removing that fixed the issue.

2 Likes