Closed christasich closed 1 year ago
Of course, right after I submitted this. I started getting the issue in v0.77.0. So it seems downgrading does not resolve it for me. Of note though is that the "WSL > Show log" option does work in =<0.77.0, but not in v0.78.0. I think this is a larger issue likely related to WSL itself.
It looks like the issue was just identified here https://github.com/microsoft/WSL/issues/9947 and a fix is in bound.
In the latest version of remote-wsl (0.78.0), vscode intermittently does not foward ports to Windows. This can sometimes be resolved (or caused) by restarting WSL (
wsl.exe --shutdown
).I first encountered this error while trying to view a PDF in WSL using the Latex Workshop extension. The PDF is served on a random port that is then accessed remotely (
127.0.0.1:PORT
).ss -tulpn
shows that the ports are setup correctly on the WSL side, butnmap
shows the matching ports as closed on the Windows side. James-Yu/LaTex-Workshop/#3826 may be referencing this same issue. Downgrading to v0.77.0 fixes the issue for me.Possibly related: I'm using a split tunnel VPN (Wireguard) for DNS resolution.
VSCode Version: Version: 1.78.0-insider (user setup) Commit: 079272e4a37ceecd22dcebc3566bb46c8580a13c Date: 2023-04-11T11:02:59.946Z Electron: 22.4.4 Chromium: 108.0.5359.215 Node.js: 16.17.1 V8: 10.8.168.25-electron.0 OS: Windows_NT x64 10.0.23430 Sandboxed: Yes
Local OS Version: Windows 11 (22H2 OS Build 23430.1000) - Insider Preview (Dev Channel)
Remote OS Version: Ubuntu 22.04.2 LTS (5.15.90.1-microsoft-standard-WSL2)
Remote Extension/Connection Type: WSL (ms-vscode-remote.remote-wsl-0.78.0)
Logs:
exthost.log
For comparison, here's the log from v0.77.0.
exthost.log (v0.77.0)
Steps to Reproduce:
code-insiders --install-extension ms-vscode-remote.remote-wsl@0.77.0
)code-insiders --install-extension ms-vscode-remote.remote-wsl@0.78.0
)[error] CodeWindow: failed to load (reason: ERR_CONNECTION_REFUSED, code: -102)
)Does this issue occur when you try this locally?: No
Note: Enabling setting
remote.WSL.debug
totrue
prevents WSL from starting at all in v0.78.0. The log shows an endless loop ofresolveAuthority(wsl,1)
(below) and no log file is created on the Windows side at%APPDATA%\Code - Insiders\logs\
.exthost.log (v0.78.0) with remote.WSL.debug enabled