Jupyter Hub Servers are started unnecessarily

[stviaene-si]

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).

[Yefee]

This is also related to connected to a named sever.

[wietzesuijker]

Adding "jupyter.disableJupyterAutoStart": true, to your settings.json seems to resolve the issue (microsoft/vscode-jupyter#1269 (comment)).

[DonJayamanne]

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

• Jupyter extension will ask Jupyter Hub for the Url of the server
• Jupyter Hub has no idea why the Url is being requested
  • It could be because the user is about to run a notebook, hence user needs to select a kernel
  • It could be because the user opens a notebook that was previously executeb by a kernel from Jupyter hub,
  • etc

In all of these cases, Jupyter Hub has idea about the context, hence will start the server regardless.

[DonJayamanne]

Suggestion:

(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