Repository navigation
Process picker dropdown does not show on WSL environment. #17859
Description
Activity
- changed the title
[-]Process picker dropdown does not show on WLS environment.[/-][+]Process picker dropdown does not show on WSL environment.[/+]on Oct 27, 2021 杜世橋 Du Shiqiao (@lucidfrontier45) Can you see if this command works for you in WSL?
ps axww -o pid=,comm=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,args=This is what we use to get the process information, and if the command fails then the picker won't show up. Also, which OS do you have under WSL?
I use Ubuntu 20.04 on WSL2.
That command works. I suspect it is a UI issue.I can replicate this same behavior on Windows 10 + WSL2 + Ubuntu 20.04 as well. The picker dialog never opens. When I run that command I get the following output (lightly sanitized):
1 init /init 12 init /init 13 init /init 14 bash -bash 4367 init /init 4368 init /init 4369 sh sh -c "$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" ccbaa2d27e38e5afa3e5c21c1c7bef4657064247 stable .vscode-server 0 4370 sh sh /mnt/c/Users/(removed)/.vscode/extensions/ms-vscode-remote.remote-wsl-0.58.5/scripts/wslServer.sh ccbaa2d27e38e5afa3e5c21c1c7bef4657064247 stable .vscode-server 0 4376 sh sh /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/server.sh --port=0 --use-host-proxy --without-browser-env-var --disable-websocket-compression --print-ip-address --enable-remote-auto-shutdown 4378 node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/out/vs/server/main.js --port=0 --use-host-proxy --without-browser-env-var --disable-websocket-compression --print-ip-address --enable-remote-auto-shutdown 4389 node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/out/bootstrap-fork --type=ptyHost 4655 node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/out/bootstrap-fork --type=watcherServiceChokidar 4682 node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/out/bootstrap-fork --type=extensionHost --uriTransformerPath=/home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/out/vs/server/uriTransformer.js --useHostProxy= 4727 bash /usr/bin/bash 5087 node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/node /home/mike/.vscode-server/extensions/ms-python.vscode-pylance-2021.11.2/dist/server.bundle.js --cancellationReceive=file:4bf2e10f610128c8cc0fa603ba2a69c3c2f06e8113 --node-ipc --clientProcessId=4682 5624 bash /usr/bin/bash 7417 node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/node /home/mike/.vscode-server/extensions/ms-azuretools.vscode-docker-1.18.0/dist/dockerfile-language-server-nodejs/lib/server.js --node-ipc --node-ipc --clientProcessId=4682 7424 node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/node /home/mike/.vscode-server/extensions/ms-azuretools.vscode-docker-1.18.0/dist/compose-language-service/lib/server.js --node-ipc --node-ipc --clientProcessId=4682 7459 node npm 7470 sh sh -c uvicorn api.app.main:app --reload --port 8000 --env-file ./api/.env 7471 uvicorn /home/mike/src/self/110yards/.env/bin/python /home/mike/src/self/110yards/.env/bin/uvicorn api.app.main:app --reload --port 8000 --env-file ./api/.env 7472 python /home/mike/src/self/110yards/.env/bin/python -c from multiprocessing.resource_tracker import main;main(4) 7473 python /home/mike/src/self/110yards/.env/bin/python -c from multiprocessing.spawn import spawn_main; spawn_main(tracker_fd=5, pipe_handle=7) --multiprocessing-fork 7511 node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/node /home/mike/.vscode-server/bin/ccbaa2d27e38e5afa3e5c21c1c7bef4657064247/extensions/json-language-features/server/dist/node/jsonServerMain --node-ipc --clientProcessId=4682 7680 ps ps axww -o pid=,comm=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,args= 16294 init /init 16295 init /init 16296 bash -bash 23915 init /init 23916 init /init 23917 docker-desktop- /mnt/wsl/docker-desktop/docker-desktop-proxy --distro-name Ubuntu-20.04 --docker-desktop-root /mnt/wsl/docker-desktop 23924 init /init 23925 docker docker serve --address unix:///home/mike/.docker/run/docker-cli-api.sockHaving the same issue here.
Version: 1.63.2 (user setup)
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:53:24.645Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT ia32 10.0.22533I am able to reproduce this in WSL.
Same problem.
Hoping issue is resolved soon! Current workaround I have been using is passing processId directly into the launch.json.
Example:
This seems to be caused by screen size error in ps.
VS Code issue related to this: microsoft/vscode#75932
PR ensuring the error is reported: #20741This issue is duplicate of: #16921
- locked as resolved and limited conversation to collaborators
on Apr 20, 2023
Environment data
Version: 1.61.2 (user setup)
Commit: 6cba118ac49a1b88332f312a8f67186f7f3c1643
Date: 2021-10-19T14:57:20.575Z
Electron: 13.5.1
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043
Python_ext: v2021.10.1365161279
Expected behaviour
Dropdown shows up as below (Windows native environment)
Actual behaviour
Dropdown does not show up.
Steps to reproduce:
1 Open a WSL project with Remote-WSL extention.
2 Create a debug configuration in the launch.json with default
Python: Attach using Process Idtemplate.{ "version": "0.2.0", "configurations": [ { "name": "Python: Attach using Process Id", "type": "python", "request": "attach", "processId": "${command:pickProcess}" }, ] }3 In
Run and Debugside pane select the above debug task.possibly related #14678