Python: Attach using Process Id no longer prompting for process
See original GitHub issueEnvironment data
- VS Code version: Latest, I just reinstalled
- Extension version (available under the Extensions sidebar): 2020.10.332292344
- OS and version: Windows 10 64bit 1909 (upgraded to 20H2, same issue)
- Python version (& distribution if applicable, e.g. Anaconda): 3.6
- Type of virtual environment used (N/A | venv | virtualenv | conda | …):N/A
- Relevant/affected Python packages and their versions: XXX
- Relevant/affected Python-related VS Code extensions and their versions: XXX
- Value of the
python.languageServer
setting: XXX
[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'
), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
Able to attach to ProcessID
launch.json: { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 “version”: “0.2.0”, “configurations”: [ { “name”: “Python: Attach using Process Id”, “type”: “python”, “request”: “attach”, “processId”: “${command:pickProcess}” } ] }
Actual behaviour
Never get prompted to pick process. If I put the actual processID in the string it catches thebreakpoint.
Steps to reproduce:
enter the above then run the debugger
Logs
Nothing that seems relevant
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:9 (1 by maintainers)
Top GitHub Comments
The next release will have the fix.
Upstream VSCode issue being tracked here: https://github.com/microsoft/vscode/issues/110432
As a workaround, please use VSCode version <=1.50