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.
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 https://github.com/SchoofsKelvin/vscode-sshfs/issues/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?
@egamma I found https://github.com/Microsoft/vscode/issues/68808 has the on-deck tag on it. I would hope this means this issue will also get 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
Most helpful comment
Any update on when this will be addressed?