Second instance of Jupyter-Lab with similar state as the first instance #16210
Comments
jupyterlab-probot
bot
added
the
status:Needs Triage
|
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
|
@chbrandt it appears that your instances might share the workspaces directory: If you want them independent you need to configure the paths to be in different places. For example, JupyterLab Desktop does it for users automatically. |
|
Hi @krassowski , thanks for this answer. While workspaces are a great feature (besides being necessary, afaiu), it felt strange to me, to have the same workspace being used by two different instances. Is this the expected behaviour? |
|
I think it may be the expected behavior when you run two servers from the same root directory, although I agree with you that it seems surprising. |
JasonWeill
added
status:Needs Discussion
and removed
status:Needs Triage
|
Hi @JasonWeill . That was a nice observation (ie, "when running servers from the same root directory"), I went to check that; The same behaviour happens when starting the servers from different directories. Check below the four screenshots representing the four servers I instantiated.
|
Yes, because by default the workspaces directory, a.k.a This would be solved by implementing #12916 Project support via a hidden directory (which is what JupyterLab Desktop does). Should we close this issue as a duplicate of #11120? |
Separately, maybe worth asking: if JupyterLab Desktop solves it well, should we just recommend it to users over installation of barebone JupyterLab for this kind of a local use case? What are the key pain points that prevent users from using JupyterLab Desktop? |
|
Closing this in favour of the discussion in #11120 (same issue) and the proposal in #12916 (project folder). How can I help to make |
|
#12916 would probably need to be implemented in
Its a deep dive across the core of the application, but it should not be too time-consuming because the codebase is actually small here (just need to flip back and forth between |
Description
After starting a few kernels in the first Jupyter-Lab instance (let's call it "8888"), I start another instance (8889).
The second instance, though, will start the same number of console, terminal, and notebook tabs as the first one.
Screenshot of instance "8888" (the first one):
Screenshot of instance "8889" (the second one):
Reproduce
Expected behavior
I would expect a new instance of Jupyter-Lab to start fresh, with only the (default) "Launcher" tab open.
Context
Troubleshoot Output
Command Line Output
$ jupyter lab [I 2024-04-18 16:46:17.985 ServerApp] jupyter_lsp | extension was successfully linked. [I 2024-04-18 16:46:17.989 ServerApp] jupyter_server_terminals | extension was successfully linked. [I 2024-04-18 16:46:17.993 ServerApp] jupyterlab | extension was successfully linked. [I 2024-04-18 16:46:17.996 ServerApp] Writing Jupyter server cookie secret to /Users/chbrandt/Library/Jupyter/runtime/jupyter_cookie_secret [I 2024-04-18 16:46:18.301 ServerApp] notebook_shim | extension was successfully linked. [I 2024-04-18 16:46:18.340 ServerApp] notebook_shim | extension was successfully loaded. [I 2024-04-18 16:46:18.342 ServerApp] jupyter_lsp | extension was successfully loaded. [I 2024-04-18 16:46:18.344 ServerApp] jupyter_server_terminals | extension was successfully loaded. [I 2024-04-18 16:46:18.345 LabApp] JupyterLab extension loaded from /opt/miniconda3/envs/jupyter/lib/python3.12/site-packages/jupyterlab [I 2024-04-18 16:46:18.346 LabApp] JupyterLab application directory is /opt/miniconda3/envs/jupyter/share/jupyter/lab [I 2024-04-18 16:46:18.346 LabApp] Extension Manager is 'pypi'. [I 2024-04-18 16:46:18.394 ServerApp] jupyterlab | extension was successfully loaded. [I 2024-04-18 16:46:18.395 ServerApp] Serving notebooks from local directory: /Users/chbrandt [I 2024-04-18 16:46:18.395 ServerApp] Jupyter Server 2.14.0 is running at: [I 2024-04-18 16:46:18.395 ServerApp] http://localhost:8888/lab?token=c666e684c3c51216812ed546b1638cb3ba53c198e0d24702 [I 2024-04-18 16:46:18.395 ServerApp] http://127.0.0.1:8888/lab?token=c666e684c3c51216812ed546b1638cb3ba53c198e0d24702 [I 2024-04-18 16:46:18.395 ServerApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation). [C 2024-04-18 16:46:18.406 ServerApp] To access the server, open this file in a browser: file:///Users/chbrandt/Library/Jupyter/runtime/jpserver-72268-open.html Or copy and paste one of these URLs: http://localhost:8888/lab?token=c666e684c3c51216812ed546b1638cb3ba53c198e0d24702 http://127.0.0.1:8888/lab?token=c666e684c3c51216812ed546b1638cb3ba53c198e0d24702 [I 2024-04-18 16:46:18.435 ServerApp] Skipped non-installed server(s): bash-language-server, dockerfile-language-server-nodejs, javascript-typescript-langserver, jedi-language-server, julia-language-server, pyright, python-language-server, python-lsp-server, r-languageserver, sql-language-server, texlab, typescript-language-server, unified-language-server, vscode-css-languageserver-bin, vscode-html-languageserver-bin, vscode-json-languageserver-bin, yaml-language-server [W 2024-04-18 16:46:20.769 LabApp] Could not determine jupyterlab build status without nodejs [I 2024-04-20 08:40:23.880 ServerApp] Kernel started: a2c78e2c-d9ea-43cb-aa1d-4f46d3fd7808 0.00s - Debugger warning: It seems that frozen modules are being used, which may 0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off 0.00s - to python to disable frozen modules. 0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation. [I 2024-04-20 08:40:24.786 ServerApp] Connecting to kernel a2c78e2c-d9ea-43cb-aa1d-4f46d3fd7808. [I 2024-04-20 08:40:24.788 ServerApp] Connecting to kernel a2c78e2c-d9ea-43cb-aa1d-4f46d3fd7808. [I 2024-04-20 08:40:24.790 ServerApp] Connecting to kernel a2c78e2c-d9ea-43cb-aa1d-4f46d3fd7808. [I 2024-04-20 08:43:09.989 ServerApp] Kernel started: 532d0852-e677-4db7-9736-27cb7ca9e6f8 [I 2024-04-20 08:43:10.671 ServerApp] Connecting to kernel 532d0852-e677-4db7-9736-27cb7ca9e6f8. [I 2024-04-20 08:43:10.673 ServerApp] Connecting to kernel 532d0852-e677-4db7-9736-27cb7ca9e6f8. [I 2024-04-20 08:43:10.675 ServerApp] Connecting to kernel 532d0852-e677-4db7-9736-27cb7ca9e6f8. [I 2024-04-20 08:44:00.543 ServerApp] Kernel started: 10a3f0b2-627f-4d69-a4b4-bf21b0d97c5e [I 2024-04-20 08:44:01.138 ServerApp] Connecting to kernel 10a3f0b2-627f-4d69-a4b4-bf21b0d97c5e. [I 2024-04-20 08:44:01.140 ServerApp] Connecting to kernel 10a3f0b2-627f-4d69-a4b4-bf21b0d97c5e. [I 2024-04-20 08:44:01.142 ServerApp] Connecting to kernel 10a3f0b2-627f-4d69-a4b4-bf21b0d97c5e. [I 2024-04-20 08:56:35.535 ServerApp] New terminal with automatic name: 1 [I 2024-04-20 09:28:43.181 ServerApp] Connecting to kernel a2c78e2c-d9ea-43cb-aa1d-4f46d3fd7808. [I 2024-04-20 09:28:43.204 ServerApp] Connecting to kernel 532d0852-e677-4db7-9736-27cb7ca9e6f8. [I 2024-04-20 09:28:43.230 ServerApp] Connecting to kernel 10a3f0b2-627f-4d69-a4b4-bf21b0d97c5e. [W 2024-04-20 09:28:43.265 LabApp] Could not determine jupyterlab build status without nodejs [I 2024-04-20 09:28:43.799 ServerApp] Connecting to kernel 532d0852-e677-4db7-9736-27cb7ca9e6f8. [I 2024-04-20 09:28:43.813 ServerApp] Connecting to kernel 10a3f0b2-627f-4d69-a4b4-bf21b0d97c5e. [I 2024-04-20 09:28:43.838 ServerApp] Connecting to kernel a2c78e2c-d9ea-43cb-aa1d-4f46d3fd7808.$ jupyter lab [I 2024-04-20 08:57:32.560 ServerApp] jupyter_lsp | extension was successfully linked. [I 2024-04-20 08:57:32.564 ServerApp] jupyter_server_terminals | extension was successfully linked. [I 2024-04-20 08:57:32.567 ServerApp] jupyterlab | extension was successfully linked. [I 2024-04-20 08:57:32.766 ServerApp] notebook_shim | extension was successfully linked. [I 2024-04-20 08:57:32.797 ServerApp] notebook_shim | extension was successfully loaded. [I 2024-04-20 08:57:32.799 ServerApp] jupyter_lsp | extension was successfully loaded. [I 2024-04-20 08:57:32.800 ServerApp] jupyter_server_terminals | extension was successfully loaded. [I 2024-04-20 08:57:32.801 LabApp] JupyterLab extension loaded from /opt/miniconda3/envs/jupyter/lib/python3.12/site-packages/jupyterlab [I 2024-04-20 08:57:32.801 LabApp] JupyterLab application directory is /opt/miniconda3/envs/jupyter/share/jupyter/lab [I 2024-04-20 08:57:32.802 LabApp] Extension Manager is 'pypi'. [I 2024-04-20 08:57:32.818 ServerApp] jupyterlab | extension was successfully loaded. [I 2024-04-20 08:57:32.819 ServerApp] The port 8888 is already in use, trying another port. [I 2024-04-20 08:57:32.819 ServerApp] Serving notebooks from local directory: /Users/chbrandt [I 2024-04-20 08:57:32.819 ServerApp] Jupyter Server 2.14.0 is running at: [I 2024-04-20 08:57:32.819 ServerApp] http://localhost:8889/lab?token=3d0e29bf3a91552d02d300f137291e9522b75ac448075a71 [I 2024-04-20 08:57:32.819 ServerApp] http://127.0.0.1:8889/lab?token=3d0e29bf3a91552d02d300f137291e9522b75ac448075a71 [I 2024-04-20 08:57:32.819 ServerApp] Use Control-C to stop this server and shut down all kernels (twice to skip confirmation). [C 2024-04-20 08:57:32.828 ServerApp] To access the server, open this file in a browser: file:///Users/chbrandt/Library/Jupyter/runtime/jpserver-85957-open.html Or copy and paste one of these URLs: http://localhost:8889/lab?token=3d0e29bf3a91552d02d300f137291e9522b75ac448075a71 http://127.0.0.1:8889/lab?token=3d0e29bf3a91552d02d300f137291e9522b75ac448075a71 [I 2024-04-20 08:57:32.913 ServerApp] Skipped non-installed server(s): bash-language-server, dockerfile-language-server-nodejs, javascript-typescript-langserver, jedi-language-server, julia-language-server, pyright, python-language-server, python-lsp-server, r-languageserver, sql-language-server, texlab, typescript-language-server, unified-language-server, vscode-css-languageserver-bin, vscode-html-languageserver-bin, vscode-json-languageserver-bin, yaml-language-server [W 2024-04-20 08:57:34.937 LabApp] Could not determine jupyterlab build status without nodejs [I 2024-04-20 08:57:35.377 ServerApp] New terminal with automatic name: 1 [I 2024-04-20 08:57:35.530 ServerApp] Kernel started: 88f81c6e-7f43-4128-8950-953df335fb6e [I 2024-04-20 08:57:35.532 ServerApp] Kernel started: 82ff477d-9f48-463a-9874-05bbabb6613d [I 2024-04-20 08:57:35.541 ServerApp] Kernel started: c8e74a4f-5494-4185-a454-2fa9db4b21ae 0.00s - Debugger warning: It seems that frozen modules are being used, which may 0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off 0.00s - to python to disable frozen modules. 0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation. [I 2024-04-20 08:57:36.275 ServerApp] Connecting to kernel 88f81c6e-7f43-4128-8950-953df335fb6e. [I 2024-04-20 08:57:36.281 ServerApp] Connecting to kernel 82ff477d-9f48-463a-9874-05bbabb6613d. [I 2024-04-20 08:57:36.287 ServerApp] Connecting to kernel c8e74a4f-5494-4185-a454-2fa9db4b21ae. [I 2024-04-20 08:57:36.288 ServerApp] Connecting to kernel c8e74a4f-5494-4185-a454-2fa9db4b21ae. [I 2024-04-20 08:57:36.290 ServerApp] Connecting to kernel c8e74a4f-5494-4185-a454-2fa9db4b21ae. [I 2024-04-20 09:28:55.046 ServerApp] Connecting to kernel 88f81c6e-7f43-4128-8950-953df335fb6e. [I 2024-04-20 09:28:55.071 ServerApp] Connecting to kernel 82ff477d-9f48-463a-9874-05bbabb6613d. [W 2024-04-20 09:28:55.080 LabApp] Could not determine jupyterlab build status without nodejs [I 2024-04-20 09:28:55.089 ServerApp] Connecting to kernel c8e74a4f-5494-4185-a454-2fa9db4b21ae. [I 2024-04-20 09:28:55.487 ServerApp] Connecting to kernel c8e74a4f-5494-4185-a454-2fa9db4b21ae. [I 2024-04-20 09:28:55.503 ServerApp] Connecting to kernel 88f81c6e-7f43-4128-8950-953df335fb6e. [I 2024-04-20 09:28:55.519 ServerApp] Connecting to kernel 82ff477d-9f48-463a-9874-05bbabb6613d.The text was updated successfully, but these errors were encountered: