Running wsl code <path> in terminal does not return (works as with -w option)

[kanlukasz]

Description:

Something happened with running VSCode in WSL via the wsl code /var/www/app command.
Until now, after executing this command, VSCode would open in the WSL environment according to the specified path and then release the terminal. That is, it was possible to give another command in the terminal or close it.
Currently, this command behaves as if I had added the -w flag.
That is, the terminal does not release this command. It does so only after I close VSCode

ScreenGIF:

VS Code Version:

Version: 1.82.2
Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
Date: 2023-09-14T05:55:25.390Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.82.2 Chrome/114.0.5735.289 Electron/25.8.1 Safari/537.36

OS Version:

OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22621 N/A Build 22621

WSL Version:

WSL version: 1.2.5.0
Kernel version: 5.15.90.1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.2283

WSL Extension version:

v0.81.3

Potential related issues and duplicates:

• linux (WSL) - vscode when started does not release the command line (need to add & to make it run in the background) #193332
• can not open vscode in the background when using vscode in WSL2 #193321
• code command from wsl doesn't exit #193302
• Calling code . from WSL prompt does not return #62698
• Commandline hangs in wsl on Windows 11 #148582

[Temepest74]

+1

It happens even when you go the the WSL distro console and type code /app

[KnisterPeter]

Same as #188426?

[lamuertepeluda]

Same as #188426?

and same as #193328

[kanlukasz]

and same as #193328

I don't see any connection between my issue and this.

[kanlukasz]

Same as #188426?

I am not sure. Note that:

• my issue appeared only a few days ago (not sure after which update). Before that, everything was working ok
• 188426 mentions nothing about the context of wsl

[lamuertepeluda]

Sorry guys (especially @kanlukasz @KnisterPeter @devhindo) I meant #193332! I was misled by gh autosuggest while typing

[samuelshenrique]

+1 here

[ChristopherGerdes]

+1 on this issue with win11, wsl2 on a brand new machine.

note that one of the big impacts for me on this is that it's breaking my environment startup scripts since part of that is to open the repos that I'm currently working on. It's pretty annoying.

[aeschli]

duplicate of #193453