-
Notifications
You must be signed in to change notification settings - Fork 285
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-SSH Bug]: failed to connect with setting "remote.SSH.defaultExtensions" and profile function #10376
Comments
+1 |
Could you please try again after updating your editor to 1.94.2 (released this morning) and let me know if the issue continues to repro? Others are reporting that this has been fixed |
I tried it and when I connected to the remote server and As in the previous version, either delete the setting “remote.SSH.defaultExtensions” or delete all profiles except the default profile, so that it is recovered. VS Code version
Output: Remote-SSH.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/log.txt_vscode-server-cli_servers_Stable-384ff7382de624fb94dbaf6da11977bba1ecd427_log.txt |
We are having the same issue. |
Thanks for following up - will take a closer look |
This doesn't seem to be extension specific. We have about 10 in our default list and we can't get the install error to go away until we remove all of them. |
Still happening in 1.94.2 ... On the first connect after opening VS Code its fine:
But on the next connect it find a running server and loops trying to install the extensions failing each time:
until it errors with I tried I have symlinked ~/.vscode-server to a network drive, maybe that's a problem? |
Removing the symlinked ~/.vscode-server directory (which pointed to an NFS mount) and re-connecting has fixed this:
|
We have this setup but I can't remove the symlink. The home folder is way too slow so we symlink it to faster local storage. |
FWIW, I don't have a symlink, but use a non-standard path for |
Is there an existing issue for this bug?
Required Troubleshooting Steps
remote.SSH.useLocalServer
settingConnect Locally
It connects successfully
->
I have always found the Remote-SSH function convenient to use. Thank you for all your help.
When using the profile feature in combination with the “emote.SSH.defaultExtensions” setting, an error occurs when trying to open another directory using the profile and the directory cannot be opened.
Expected Behavior
To open a directory using a profile without error.
Steps To Reproduce
code ~/tmp
in remote terminalThis did not occur when using only default profile.
This did not occur when the setting was left empty.
This did not occur when using Remote-SSH 0.114.3.
Once this occurred, I had to kill all code-server related processes and delete the .vscode-server directory to get it back.
Remote-SSH Log
Remote-SSH Log
Anything else?
.vscode-server/cli/servers/Stable-e10f2369d0d9614a452462f2e01cdc4aa9486296/log.txt
.vscode-server/cli/servers/Stable-e10f2369d0d9614a452462f2e01cdc4aa9486296/pid.txt
v0.115.0
The text was updated successfully, but these errors were encountered: