Help! After updating VSCode, I can no longer connect to NixOS though the WSL remote

[nzbr]

You may have noticed that with the latest update to the WSL remote extension (0.77.0), connecting to NixOS fails.
This is because Micrsoft removed the option for setting the remote connection method. Where before you could get it to connect by setting the option to something other than wslExeProxy, that is the only option available now.

There are two issues tracking possible solutions:

• WSL (version 0.77.x) remote.WSL2.connectionMethod required microsoft/vscode-remote-release#8305 asking them to patch the alternate connection methods back in
• Environment variables do not take effect for wsl --exec #222 here for patching NixOS on WSL to support wslExeProxy

EDIT: As @purepani pointed out over at the Microsoft repo, for the time being, you can try to get it to work by downgrading the WSL Remote extension to the latest working version (0.76.0) either through the GUI or by running the following command:

code --install-extension [email protected]

and making sure that you have the following setting configured in VSCode

  "remote.WSL2.connectionMethod": "wsl2VMAddress",

[ykis-0-0]

Or if downgrading isn't desired, msteen's VSCode Server is also an option. Just my two cents here :)

[KiruyaMomochi]

Deleted. I think what occurs to me is not the same issue.

Deleted content

For me, just type code in my WSL shell, waiting for it to download vscode-server is enough.

After vscode-server is downloaded, everything is the same as before. Just use nixos-vscode-server or manually replace node under ~/.vscode-server with a symlink.

[SuperSandro2000]

While debugging why my WSL setup broke I discovered that it only wants to run uname

wsl.extraBin = with pkgs; [
  { src = "${coreutils}/bin/uname"; }
];

but the node is then unpatched. Probably patchelfing it could fix things.