VS Code stuck on opening remote with WSL about vscode HOT 12 CLOSED

When the remote window is open and you see Opening Remote... message, can you run WSL: Show Log... ?

from vscode.

@aeschli
no, it seems the extension did not fully load yet, or something of that nature

from vscode.

Anything in the dev tools console?

from vscode.

no errors / warnings in devtools, 3 logs in total, the first is large with all the settings (copied it into here https://pastebin.com/N0htuN8t)
the other two are:

DEBUG Overwriting user extension /c:/Users/user/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.2 with /c:/Users/user/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.2.

and

TRACE pickRunningLocation for ms-vscode-remote.remote-wsl, extension kinds: [ui], isInstalledLocally: true, isInstalledRemotely: false, preference: None => LocalProcess

I also checked the logs folder (C:\Users\user\AppData\Roaming\Code\logs, i'm using a user install if it matters)
It seems that when starting the vs code at that directory, two logs folders are created, the following is a link to a zip file containing both folders and the logs inside
https://mega.nz/file/czJiWQ4B#JmLCcvspgzmC8n6gpeY-yYmRS1WO3QHTBqev4BSIhu0

from vscode.

To verify wheater this is caused by something in the storage, can you try running on an new user data dir?
code-insiders --user-data-dir %TEMP%\test123

from vscode.

I tried running it directly in the wsl, (code --user-data-dir="%TEMP%\test123" .) and it ignored the option (Ignoring option 'user-data-dir': not supported for code.) and open it regularly,
but running it from powershell at the windows computer and then connecting to wsl, did work!
So we can assume it's a storage thing?

**Just to be clear, generally opening it from windows doesn't work, only with the data dir option

from vscode.

You have to run it in the Windows command prompt (not the WSL terminal)

from vscode.

You mentioned it runs the first time with a particular but never the second time?

from vscode.

You mentioned it runs the first time with a particular but never the second time?

So, I've investigated a bit more, because of that question, it think I might have found the culprit, opening it multiple times worked, until I looked at the "recommended extensions" again and added the VS Code Selfhost Test Provider, afterwards reopening the project becomes impossible

I did install in the other occasions, just did not make the connection myself

from vscode.

Oh, that's interesting. @connor4312 ...

from vscode.

I don't reproduce this, and I have no idea how that would be related to this. The selfhost test provider a test extension and nothing more

from vscode.

This is probably #212105

from vscode.