-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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
Support filesystem paths using ssh:// #66046
Comments
This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. Happy Coding! |
Please file the issue against the SSH extension. |
Per SchoofsKelvin/vscode-sshfs#31 VSCode or other extensions needs to take action because there's nothing they can do about it. |
Since builtin git is managed by VS Code, this issue is for the git extension to be updated but expecting other extension authors to support is nice but shouldn't be necessary. There has to be a way Code itself can handle it so extension authors don't. |
Any update on when this will be addressed? |
We just announced remote development with VS Code, check out the blog post for details https://code.visualstudio.com/blogs/2019/05/02/remote-development |
Steps to Reproduce:
Does this issue occur when all extensions are disabled?:
When all other extensions are disabled this is still an issue.
I believe the issue is that the SSHFS extension makes use of the FileSystemProvider API to allow workspaces to be mounted using ssh:// that appear as \ to git and thus fails to initialize. Since this API was created, Git and other extensions should be able to recognize when a local workspace created using SSH. Since this affects other extensions such as Python (when attempting to run debug or tests), I believe this is a VS Code actionable to globally allow all extensions to register this file path.
The text was updated successfully, but these errors were encountered: