Open running remote Jupyter notebooks

[mmrnustik]

VSCode should allow to open and connect to notebooks on Jupyter server visible on /tree? page.

[rchiodo]

Have you tried specifying the server URI in our "Python : Specify local or remote jupyter server"

That won't work with the /tree form, but it will if you provide the same port as the /tree form and the token you can see on the command line at startup of the server.

We require a token as a security measure.

You can also setup your jupyter notebook to require a password instead (then the token isn't necessary)

[mmrnustik]

I'm able to create new notebook connected to remote server, but I can't see notebooks already running (created and edited in web browser) and I can't see notebook created in VSCode in jupyter web interface (and I can't send link to colleague etc.).

[rchiodo]

Sounds like you want a way to view the file system on the remote server. This issue here is similar:
https://github.com/microsoft/vscode-python/issues/7956

[rchiodo]

Our workaround to this problem is to use SSH to connect to the remote machine with VS code.

[rchiodo]

Well okay that solves half of the problem. Being able to send a link to a colleague is different. I'm guessing we could support that separately.

[mmrnustik]

Our workaround to this problem is to use SSH to connect to the remote machine with VS code.
It allows me open notebooks from server, but does it allow connection to already running notebook (with result of long running computation and huge datset loaded)?

[rchiodo]

Not yet. Soon. We're working on supporting running kernels.

[Minxiangliu]

@rchiodo
Hi, I am trying to use vscode for remote jupyter.
I have started the jupyter server on linux.

but when I copy the URL in vscode(Windows), there is no response

However, the web can be accessed normally

What am i missing?

[rchiodo]

@Minxiangliu your issue is a dupe of this: microsoft/vscode#110528

VS code is not allowing the enter key to work.

[IanMatthewHuff]

I believe that this initial bug here (showing running sessions on a remote server) has been resolved, so closing this issue. I think that #1366 solves the other issues mentioned.