-
Notifications
You must be signed in to change notification settings - Fork 28.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
Failed to connect to the remote extension host server (Error: Cannot resolve authority) #150169
Comments
I'm getting a similar error. It's not consistent, as I can open folders in WSL, and I can open some workspaces without issue. But one particular workspace causes the error:
|
I've only been able to reproduce my bug twice. Both times I was inside of a workspace, so that may have been a contributing factor. Good I had not thought of that before. However I know there are other workspace related issues; the File Watcher constantly loses focus within an open workspace, for example, so its definitely worth looking into. I'll attempt to repro with just a regular folder open vs a workspace if I get the chance. |
I figured it out. I receive |
Good catch! I can reproduce by opening a remote window, putting the Call Stack in the secondary side bar and reload.
|
I suspect this is the same as #148593, cool |
I don't know why a remote window is necessary, but I see it too. First a DebugService is created by the DisassemblyView. It gets instantiated lazily when it is accessed. Then a second one is created by CallStackView. I don't know why it doesn't get the same one that was already created. edit - also am sometimes able to repro in a local window |
This seems to also happen for me whenever I try to remote SSH into my server with a local window open. Weird. |
I believe this issue no longer reproduces in latest insiders. |
It happens all the time with remote shh tom me :( Any news how to fix it? |
@elranu are you using the latest insiders? |
Issue Type: Bug
Scenario: Reviewing/editing user-level VSCode settings in the
settings.json
file (C:\Users\%USERPROFILE%\AppData\Roaming\Code\User\settings.json
) from within a WSL window.Possibly related to #135021
Steps to Reproduce:
settings.json
and make some edits without saving them.settings.json
file, clickRequires Reload
and let the window reload.ReviewOverwrite
WaitClose & Reopen/Reload
Actual Results: Lower left-hand corner displays
⚠️ Disconnected from WSL
, and a pop-up in the lower right-hand corner reads as follows.Expected: VSCode reopens after (presumably) saving the changes to the
setting.json
file. The new WSL window renders based on the latest changes made to the user settings.VS Code version: Code 1.67.2 (c3511e6, 2022-05-17T18:15:52.058Z)
OS version: Windows_NT x64 10.0.22621
Restricted Mode: Yes
Extensions: none
A/B Experiments
The text was updated successfully, but these errors were encountered: