Can't save to remote workspace

[svechinsky]

Bug: Notebook Editor, Interactive Window, Python Editor cells

When specifying a remote Jupyter server I can successfully creat new notebooks via the command palate but I can't save them.
When I click on the save icon it just prompts saving the notebook on my local computer.
Also, it doesn't let me view other notebooks/files on the remote server.

Steps to cause the bug to occur

1. Specify a remote URI
2. Create a new notebook via command palate
3. Try and save

Actual & Expected behavior

Expected

Clicking save saves the notebook on the remote desktop
+
Being able to view other files on the remote workspace.

Actual

Clicking save prompts for a local save and I can't view other files.

Your Jupyter and/or Python environment

Please provide as much info as you readily know

• Jupyter server running: Remote
• Extension version: 2019.10.41019
• VS Code version: 1.39.1
• Setting python.jediEnabled: false
• Python and/or Anaconda version: 3.7
• OS: Ubuntu
• Virtual environment: pipenv

[svechinsky]

I just realized that perhaps this is not an intended feature and that the goal of the connect to a remote server is just to execute the notebook remotely (but to save it locally).

If that's the case then I think what I outlined above might be more of a feature suggestion instead of a bug.

[rchiodo]

You should be able to do this if you actually remote-ssh to the remote server.

See this here:
https://code.visualstudio.com/docs/remote/ssh

[harveyslash]

replying to @rchiodo, I have asked a question on stack overflow about this as well.
To summarize, is it possible to save a ipynb file that I have opened through remote ssh without having to choose the location every time I want to save it?

[rchiodo]

That shouldn't be necessary. Just hitting the save button should save the file with its current name. It shouldn't do a save as unless you create a new notebook.

[harveyslash]

AH!
I might have found a bug. If the name of the file is Untitled.ipynb, it brings up that save dialogue. ipynb files with other names dont have this issue. I will investigate further, and if you want me to, I can post an issue

[rchiodo]

Yeah that sounds like a bug. It should be checking the scheme of the file, not the name of the file. Please enter an issue.

[rchiodo]

This should be resolved. At least the remote-ssh case.

[rchiodo]

The other case is handled by this:
#1366