-
Notifications
You must be signed in to change notification settings - Fork 29.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
Using vscode://vscode-remote/ssh-remote with an SSH username can break (WebView) resources #128309
Comments
Closing since this is not reproducible on insiders. If you start seeing it again with VS Code 1.59+ please let us know |
I can reproduce this in Insiders now, see microsoft/vscode-remote-release#5282 (comment) Basically, having Remote SSH installed, open
and try to view a PNG file. That won't work due to resource requests having "user@" being blocked. I am not sure this is an issue with VS Code or VS Code Remote (SSH), though, so I am posting this in both issues. |
@mjbvz do you want to reopen and rename this issue? Or should I file the above as a new one? |
I should maybe add that while the Then, while
fails to connect,
still connects fine. |
Possibly a duplicate of #123494 Does this reproduce in the latest VS Code insiders build? |
Interesting - the issue does reproduce in Version: 1.59.0 (user setup) but not in Version: 1.60.0-insider (user setup) I can test this again once 1.60 has been released. |
Ok, closing this since it is fixed in insiders |
/verified - thanks! |
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
It's not easy to reproduce. It happens with Remote SSH, opening a remote
.workspace
file. Reproduces in first step of extension bisect, so should not be related to extensions. Does not reproduce when connecting to the same Linux server via Remote SSH (without opening the workspace). Does not reproduce locally on Windows.I also see this:
Does not happen with this version SSH-remoting into the same workspace (settings and extensions synced):
So either it has been fixed already, or my stable installation is broken somehow.
The text was updated successfully, but these errors were encountered: