Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

unable to resolve vscode-remote #210492

Open
LazyDiot opened this issue Apr 16, 2024 · 1 comment
Open

unable to resolve vscode-remote #210492

LazyDiot opened this issue Apr 16, 2024 · 1 comment
Assignees
@aeschli

Comments

@LazyDiot
Copy link

LazyDiot commented Apr 16, 2024 •
edited

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.88.1
  • OS Version: Windows_NT x64 10.0.19045

Hello.
I can't seem to open a folder which i opened earlier.
I worked on it tonight (around 4.00 am). I shut down the computer. I turn it on again around 12.00. VScode starts and loads said folder and files. I don't intend to work on it at the time so I close it. I'm trying to open it via WSL terminal around 16.45, and I get this error :
https://i.gyazo.com/thumb/1200/8c8ec26bc0604409d687f4b41106716a-png.jpg.
As I'm really unfamiliar with this, I don't know what could have happened since i wasn't even on my computer during this timelapse and nothing was running.
I tried restarting my computer, and uninstalling/reinstalling in between.
As for debug info, this is the output :
VSCODE_WSL_DEBUG_INFO=true code

  • COMMIT=e170252f762678dec6ca2cc69aba1570769a5d39
  • APP_NAME=code
  • QUALITY=stable
  • NAME=Code
  • SERVERDATAFOLDER=.vscode-server
  • realpath /mnt/c/Users/D/AppData/Local/Programs/Microsoft VS Code/bin/code
  • dirname /mnt/c/Users/D/AppData/Local/Programs/Microsoft VS Code/bin/code
  • dirname /mnt/c/Users/D/AppData/Local/Programs/Microsoft VS Code/bin
  • VSCODE_PATH=/mnt/c/Users/D/AppData/Local/Programs/Microsoft VS Code
  • ELECTRON=/mnt/c/Users/D/AppData/Local/Programs/Microsoft VS Code/Code.exe
  • IN_WSL=false
  • [ -n Ubuntu ]
  • IN_WSL=true
  • [ true = true ]
  • export WSLENV=ELECTRON_RUN_AS_NODE/w:WT_SESSION:WT_PROFILE_ID:
  • wslpath -m /mnt/c/Users/D/AppData/Local/Programs/Microsoft VS Code/resources/app/out/cli.js
  • CLI=C:/Users/D/AppData/Local/Programs/Microsoft VS Code/resources/app/out/cli.js
  • WSL_EXT_ID=ms-vscode-remote.remote-wsl
  • ELECTRON_RUN_AS_NODE=1 /mnt/c/Users/D/AppData/Local/Programs/Microsoft VS Code/Code.exe C:/Users/D/AppData/Local/Programs/Microsoft VS Code/resources/app/out/cli.js --locate-extension ms-vscode-remote.remote-wsl
  • cat /tmp/remote-wsl-loc.txt
  • WSL_EXT_WLOC=c:\Users\D.vscode\extensions\ms-vscode-remote.remote-wsl-0.88.0
  • [ -n c:\Users\D.vscode\extensions\ms-vscode-remote.remote-wsl-0.88.0 ]
  • wslpath -u c:\Users\D.vscode\extensions\ms-vscode-remote.remote-wsl-0.88.0
  • WSL_CODE=/mnt/c/Users/D/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh
  • /mnt/c/Users/D/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh e170252 stable /mnt/c/Users/D/AppData/Local/Programs/Microsoft VS Code/Code.exe code .vscode-server
  • [ -z .vscode-server ]
  • [ .vscode-server = .vscode-insiders ]
  • [ ! -t 0 ]
  • VSCODE_REMOTE_BIN=/home/lazydiot/.vscode-server/bin
  • AUTHORITY=wsl+default
  • [ Ubuntu ]
  • AUTHORITY=wsl+Ubuntu
  • dirname /mnt/c/Users/D/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh
  • /mnt/c/Users/D/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslDownload.sh e170252 stable /home/lazydiot/.vscode-server/bin
  • [ ! -d /home/lazydiot/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39 ]
  • RC=0
  • [ 0 -eq 100 ]
  • [ 0 -ne 0 ]
  • mktemp /tmp/vscode-distro-env.XXXXXX
  • STORED_ENV=/tmp/vscode-distro-env.C5kZzz
  • env
  • dirname /mnt/c/Users/D/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh
  • VSCODE_CLIENT_COMMAND=/mnt/c/Users/D/AppData/Local/Programs/Microsoft VS Code/Code.exe VSCODE_CLIENT_COMMAND_CWD=/mnt/c/Users/D/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts VSCODE_CLI_AUTHORITY=wsl+Ubuntu VSCODE_CLI_REMOTE_ENV=/tmp/vscode-distro-env.C5kZzz VSCODE_STDIN_FILE_PATH= WSLENV=VSCODE_CLI_REMOTE_ENV/w:ELECTRON_RUN_AS_NODE/w:WT_SESSION:WT_PROFILE_ID: /home/lazydiot/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/bin/remote-cli/code
    /mnt/c/Users/D/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh: 68: /home/lazydiot/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/bin/remote-cli/code: not found
  • exit 127
@matthewdrees
Copy link

Same as LazyDiot, even the timing.

Everything working on Tuesday, April 16. On Wednesday, April 17, got the same error messages from starting VSCode on Windows...

[2024-04-19 18:26:21.203] Extension version: 0.88.0
[2024-04-19 18:26:21.203] L10N bundle: undefined
[2024-04-19 18:26:21.254] authorityHierarchy: wsl+Ubuntu-20.04
[2024-04-19 18:26:21.254] WSL extension activating for a local WSL instance
[2024-04-19 18:26:21.263] Resolving wsl+Ubuntu-20.04, resolveAttempt: 1
[2024-04-19 18:26:21.264] NodeExecServer run: C:\WINDOWS\System32\wsl.exe --status
[2024-04-19 18:26:21.380] WSL feature installed: true (wsl --status)
[2024-04-19 18:26:21.380] NodeExecServer run: C:\WINDOWS\System32\wsl.exe --list --verbose
[2024-04-19 18:26:21.497] 3 distros found
[2024-04-19 18:26:21.498] Starting VS Code Server inside WSL (wsl2)
[2024-04-19 18:26:21.498] Windows build: 22631. Multi distro support: available. WSL path support: enabled
[2024-04-19 18:26:21.499] Scriptless setup: false
[2024-04-19 18:26:21.500] No shell environment set or found for current distro.
[2024-04-19 18:26:21.663] WSL daemon log file: 
[2024-04-19 18:26:21.667] Probing if server is already installed: if [ -d ~/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39 ]; then printf 'install-found '; fi; if [ -f /etc/alpine-release ]; then printf 'alpine-'; fi; if [ -s ~/.vscode-server/bin/compatibilty-check ]; then printf 'legacy-'; fi; uname -m;
[2024-04-19 18:26:21.667] NodeExecServer run: C:\WINDOWS\System32\wsl.exe -d Ubuntu-20.04 -e sh -c if [ -d ~/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39 ]; then printf 'install-found '; fi; if [ -f /etc/alpine-release ]; then printf 'alpine-'; fi; if [ -s ~/.vscode-server/bin/compatibilty-check ]; then printf 'legacy-'; fi; uname -m;
[2024-04-19 18:26:21.835] Probing result: install-found x86_64
[2024-04-19 18:26:21.836] Server install found in WSL
[2024-04-19 18:26:21.836] NodeExecServer run: C:\WINDOWS\System32\wsl.exe -d Ubuntu-20.04 sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" e170252f762678dec6ca2cc69aba1570769a5d39 stable code-server .vscode-server --host=127.0.0.1 --port=0 --connection-token=1236154508-2935562482-3373952719-284753848 --use-host-proxy --without-browser-env-var --disable-websocket-compression --accept-server-license-terms --telemetry-level=all'
[2024-04-19 18:26:22.006] Setting up server environment: Looking for /home/mdrees/.vscode-server/server-env-setup. Not found.
[2024-04-19 18:26:22.006] WSL version: 5.15.146.1-microsoft-standard-WSL2 Ubuntu-20.04
[2024-04-19 18:26:22.006] WSL-shell-PID: 456
[2024-04-19 18:26:22.006] Node executable: /home/mdrees/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/node
[2024-04-19 18:26:22.006] Starting server: /home/mdrees/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/bin/code-server --host=127.0.0.1 --port=0 --connection-token=1236154508-2935562482-3373952719-284753848 --use-host-proxy --without-browser-env-var --disable-websocket-compression --accept-server-license-terms --telemetry-level=all
[2024-04-19 18:26:22.006] /mnt/c/Users/mattd/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslServer.sh: 50: /home/mdrees/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/bin/code-server: not found
[2024-04-19 18:26:22.006] For help with startup problems, go to https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips
[2024-04-19 18:26:22.007] NodeExecServer run: C:\WINDOWS\System32\wsl.exe -d Ubuntu-20.04 -e kill 456
[2024-04-19 18:26:25.671] Download in background is enabled

... or from running "code ." from a folder on WSL:

$ VSCODE_WSL_DEBUG_INFO=true code .
+ COMMIT=e170252f762678dec6ca2cc69aba1570769a5d39
+ APP_NAME=code
+ QUALITY=stable
+ NAME=Code
+ SERVERDATAFOLDER=.vscode-server
+ realpath /mnt/c/Users/mattd/AppData/Local/Programs/Microsoft VS Code/bin/code
+ dirname /mnt/c/Users/mattd/AppData/Local/Programs/Microsoft VS Code/bin/code
+ dirname /mnt/c/Users/mattd/AppData/Local/Programs/Microsoft VS Code/bin
+ VSCODE_PATH=/mnt/c/Users/mattd/AppData/Local/Programs/Microsoft VS Code
+ ELECTRON=/mnt/c/Users/mattd/AppData/Local/Programs/Microsoft VS Code/Code.exe
+ IN_WSL=false
+ [ -n Ubuntu-20.04 ]
+ IN_WSL=true
+ [ true = true ]
+ export WSLENV=ELECTRON_RUN_AS_NODE/w:
+ wslpath -m /mnt/c/Users/mattd/AppData/Local/Programs/Microsoft VS Code/resources/app/out/cli.js
+ CLI=C:/Users/mattd/AppData/Local/Programs/Microsoft VS Code/resources/app/out/cli.js
+ WSL_EXT_ID=ms-vscode-remote.remote-wsl
+ ELECTRON_RUN_AS_NODE=1 /mnt/c/Users/mattd/AppData/Local/Programs/Microsoft VS Code/Code.exe C:/Users/mattd/AppData/Local/Programs/Microsoft VS Code/resources/app/out/cli.js --locate-extension ms-vscode-remote.remote-wsl
+ cat /tmp/remote-wsl-loc.txt
+ WSL_EXT_WLOC=c:\Users\mattd\.vscode\extensions\ms-vscode-remote.remote-wsl-0.88.0
+ [ -n c:\Users\mattd\.vscode\extensions\ms-vscode-remote.remote-wsl-0.88.0 ]
+ wslpath -u c:\Users\mattd\.vscode\extensions\ms-vscode-remote.remote-wsl-0.88.0
+ WSL_CODE=/mnt/c/Users/mattd/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh
+ /mnt/c/Users/mattd/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh e170252f762678dec6ca2cc69aba1570769a5d39 stable /mnt/c/Users/mattd/AppData/Local/Programs/Microsoft VS Code/Code.exe code .vscode-server .
+ [ -z .vscode-server ]
+ [ .vscode-server = .vscode-insiders ]
+ [ ! -t 0 ]
+ VSCODE_REMOTE_BIN=/home/mdrees/.vscode-server/bin
+ AUTHORITY=wsl+default
+ [ Ubuntu-20.04 ]
+ AUTHORITY=wsl+Ubuntu-20.04
+ dirname /mnt/c/Users/mattd/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh
+ /mnt/c/Users/mattd/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslDownload.sh e170252f762678dec6ca2cc69aba1570769a5d39 stable /home/mdrees/.vscode-server/bin
+ [ ! -d /home/mdrees/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39 ]
+ RC=0
+ [ 0 -eq 100 ]
+ [ 0 -ne 0 ]
+ mktemp /tmp/vscode-distro-env.XXXXXX
+ STORED_ENV=/tmp/vscode-distro-env.6dA2MD
+ env
+ dirname /mnt/c/Users/mattd/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh
+ VSCODE_CLIENT_COMMAND=/mnt/c/Users/mattd/AppData/Local/Programs/Microsoft VS Code/Code.exe VSCODE_CLIENT_COMMAND_CWD=/mnt/c/Users/mattd/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts VSCODE_CLI_AUTHORITY=wsl+Ubuntu-20.04 VSCODE_CLI_REMOTE_ENV=/tmp/vscode-distro-env.6dA2MD VSCODE_STDIN_FILE_PATH= WSLENV=VSCODE_CLI_REMOTE_ENV/w:ELECTRON_RUN_AS_NODE/w: /home/mdrees/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/bin/remote-cli/code .
/mnt/c/Users/mattd/.vscode/extensions/ms-vscode-remote.remote-wsl-0.88.0/scripts/wslCode.sh: 68: /home/mdrees/.vscode-server/bin/e170252f762678dec6ca2cc69aba1570769a5d39/bin/remote-cli/code: not found
+ exit 127

... FYI no "bin" folder:

$ ls .vscode-remote-containers/bin/e170252f762678dec6ca2cc69aba1570769a5d39/
LICENSE  node  node_modules

@roblourens roblourens assigned aeschli and unassigned roblourens Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aeschli aeschli

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@roblourens @matthewdrees @aeschli @VSCodeTriageBot @LazyDiot