redhat-developer / redhat-developer/vscode-quarkus
Debugging capability should support random ports
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 79
- Forks
- 31
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 6
Description
As per https://twitter.com/maxandersen/status/1719295806795026479 .
Currently we debug using a launch task that launches Quarkus in dev mode and connects to port 5005. If the port becomes randomized (due to a conflict) I think we'll need to de-couple the pre-launch task from the debug launch, and add some kind of listener into the logs to detect the change. Then we can launch the debug task independently on the new port.
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 with src/wizards/debugging/LaunchConfigCreator.ts around lines 100-105 and review how the pre-launch task and debug launch currently use port 5005. Trace the dev-mode logs and debug configuration flow; done means a randomized port caused by a conflict is detected and the debug task connects to that new port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100