Vscode-remote-release: Code-insiders started from WSL doesn't return to console/ doesn't connect

[Sieboldianus]

Intro:

• I've reported this problem before here in #780, it was solved but since the update yesterday the bug seems back
• I've searched and found 2 similar problems, but no solution reported there works for me and, even when following the guidance, my issue remains. See 46462
  and 44540
• I've installed the latest code-insiders release
• VSCode Version: 1.39.0-insider (user setup)
• OS Version: Windows 10 with latest patches

Steps to Reproduce:

1. Install Code-Insiders
2. Open WSL
3. type code-insiders .
4. a: Code insiders opens up in Windows, does not connect to WSL
5. b: WSL shows log output from code-insiders, e.g.:

[main 2019-09-05T11:06:09.080Z] update#setState idle
[main 2019-09-05T11:06:39.081Z] update#setState checking for updates
[main 2019-09-05T11:06:39.106Z] update#setState idle

• same result when launching with code-insiders . --disable-extensions, launching with code . opens up regular vs code (doesn't leak, but also has no native WSL support). So, does this issue occur when all extensions are disabled? Yes!

My Path environment variables for code and code-insiders:

which code-insiders
/c/Users/[me]/AppData/Local/Programs/Microsoft VS Code Insiders/bin/code-insiders

which code
/c/Program Files/Microsoft VS Code/bin/code

My WSL is based on the official Ubuntu 18.04, setup with LxRunOffline

• starting code-insiders with code-insiders . from WSL worked until the last week. So this issue didn't occur before the latest version of code-insiders.

[pcolmer]

I'm having the same problem. It does seem to have been caused by a newish release as I'm using this daily and I've only started seeing this today. It was fine yesterday.

[kaymach]

Same here. Happened right after most recent update.

EDIT: Found a workaround. Just go to the very bottom left and "Open a new remote window" > "Reopen folder in WSL". Then CTRL + C in console. This will allow you to connect and use your console again.

[aeschli]

Sorry for that, I copy pasted a fix to the wrong line.
I pushed a fix. If you can't wait for the next insiders build on Monday, edit your /c/Users/[me]/AppData/Local/Programs/Microsoft VS Code Insiders/bin/code-insiders as seen here
https://github.com/microsoft/vscode/commit/68c1123b33676df276f706e66caf2293a959155b

[Sieboldianus]

Yep, tested, works again 👍