Allow multiple debug connections in VS code using the same port
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python, vscode
- Domain
- developer-experience, devtools
Research direction
The issue names no debugpy files or tests; start by tracing the --connect path and the VS Code attach configuration shown in the report. Done means one attach configuration can accept and handle multiple incoming connections on the same port.
Written by the indexing model from the issue text.
Description
Hello debugpy team, hi Pavel,
the discussion
"How to debug cmdline scripts with options used in a sequence of piped cmds with VS Code" https://github.com/microsoft/debugpy/discussions/1498
described a way to debug multiple calls of a cmdline script in a sequence of linux commands using a pipe.
In this example the debug connection has been opened from the script to a listening VS code IDE using --connect
If we have a sequence of calls like so
cat myfile | python -m debugpy --connect 5678 ./python-script-1.py --option1=x | python -m debugpy --connect 5679 python-script-2.py --option2=y
we have to use several ports and we have to start several debug sessions in VS code using their own debug settings for each port.
It would be better, if VS code would only need one debug config for multiple incoming connections and could handle them.
Example:
"name": "Python: Listen 5678",
"type": "python",
"request": "attach",
"listen": {
"host": "localhost",
"port": 5678,
"allow_multiple_connections": "true" *** NEW ***
},
},
This behaviour would be similar to PHP debugging using xdebug and VS code or PHPstrom.
Thanks a lot in advance for realizing this perhaps in the future.
Best regards, Uwe
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 202
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/debugpy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in microsoft/debugpy
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
xinnan-tech/xiaozhi-fde-talk#263 ·
-
rules
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
huggingface/Repo2RLEnv#163 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
huggingface/sentence-transformers#4074 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·