-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remote jupyter server connections for Native Notebook #254
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Use as inspo |
This comment has been minimized.
This comment has been minimized.
Hi there. The ideal workflow in my mind would be we open up a remote jupyter notebook in VSC just like what we do when normally open it in a browser: we can see a tree view of the files and can see running kernels/notebooks, and we can edit it directly, but with the strong feature language server and other plugins of VSC |
@DonJayamanne This was just marked needs-triage, but it seems like work that was already done? Leaving open for now. |
I came here from StackOverflow: https://stackoverflow.com/questions/59765486/vscode-remote-jupyter-notebook-open-an-existing-notebook-in-a-specific-folder I am confused by this thread from 2 years ago. Does VS Code support opening remote notebooks now or is this still in the "enhancement" request phase? I am also confused as a user that I am able to connect remotely to a notebook server but how do I retrieve my notebooks that are already there? Is this only for people who have local notebooks but for some reason want to have them run remotely on more powerful hardware??? |
@ejkitchen there are multiple ways to use remote. If you want to use remote hardware (because maybe the GPU is more powerful), but don't need your files on the remote machine, then you would use this command: That connects to a remote jupyter server but does NOT copy any files to the remote machine. If you want to connect to a remote machine and see all of the files in VS code, then you'd use something like Remote SSH. In the remote SSH scenario, a VS code server runs on the remote machine, serving up files to your local client. Kernels are run from this VS code server and can access all the remote files. Our long term goal is to unify these two modes so they behave the same, but we haven't gotten that far yet. |
I'm going to close this as a dupe of #1601 |
@rchiodo That doesn't work. |
Turns out, if you install the local extensions onto the remote server, it actually works. But there aren't many clues in the GUI that suggest that. Anyway, I've figured it out, it's working now. Would be nice if these features were made more explicit somehow. |
I think this feature would be really useful |
May I ask what is the current status of this feature? This seems to have been implemented but I'm not able to find any clues from the doc on how to use it. Note this is particularly different from some of the pointed issues here that users don't usually have ssh access to the jupyter notebook servers we are working on but still want to utilize VSC's strong feature. |
That is very different than what is described here as I have mentioned. The goal here is to be able open up existing Jupyter notebook URL and edit files there through VSC as a replacement of the browser. The link you shared only uses the remote kernel. Any running notebook cannot be opened up in VSC with that manner. |
You are looking for #1366 |
No description provided.
The text was updated successfully, but these errors were encountered: