Open stviaene-si opened 9 months ago
This is also related to connected to a named sever.
Adding "jupyter.disableJupyterAutoStart": true,
to your settings.json seems to resolve the issue (https://github.com/microsoft/vscode-jupyter/issues/1269#issuecomment-946162122).
Adding "jupyter.disableJupyterAutoStart": true, to your settings.json seems to resolve the issue
If that does work, its not by design. Unfortunately the way Jupyter and Jupyter Hub extensions work today is as follows
In all of these cases, Jupyter Hub has idea about the context, hence will start the server regardless.
(internal notes)
Add purpose
in the resolveJupyterServer
API call
This way the server providers will know why the server is being resolved.
However the implementation in Jupyter is more complicated than that
Would it be possible to make the extension not autostart servers if they are not alive?
I often have multiple Jupyter notebooks open, and have a JupyterHub that I sometimes (but rarely) connect to. Every time I open vscode it starts a JupyterHub server that I'm not planning to connect to (because I have a notebook open).