microsoft / microsoft/vscode-java-debug
Process Picker broken when JVM binds to random port
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 591
- Forks
- 429
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 19
Description
When port conflicts occur, a user may choose to let the JVM bind to a random port by omitting the [address attribute] (https://docs.oracle.com/cd/E19501-01/819-3664/abgdm/index.html) or by passing address=0 as command-line arguments. This breaks the process picker because it matches on address, which is either missing or its value is 0:
A workaround is to let users manually enter the port: https://github.com/tlaplus/CommunityModules/commit/fa56d3fd1bd29dbfc9449a2cf711259ade5abbfc
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.
Research direction
Start at src/processPicker.ts line 9 and reproduce the picker with a JVM using an omitted address or address=0. Trace how the picker matches processes and make the random-port case selectable instead of failing; verify that users no longer need to enter the port manually.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100