Repository navigation
Process Picker broken when JVM binds to random port #1121
Description
Activity
- added a commit that references this issue
on Feb 8, 2022 Hi Markus Alexander Kuppe (@lemmy), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
-
Enhance the process picker to fall back on port‐only matching when
addressis omitted or set to0. For example, insrc/processPicker.ts:const portArg = args.get('port'); return processes.filter(p => { const addr = args.get('address'); return (addr && addr !== '0' && p.commandLine.includes(`address=${addr}`)) || p.commandLine.includes(`port=${portArg}`); });
-
Update the regex/filter in
processPicker.tsto treat missing or0address as a wildcard host and only match onport. -
As a temporary workaround, prompt the user to manually enter the port (see this example commit):
• tlaplus/CommunityModules@fa56d3f
The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
-
When port conflicts occur, a user may choose to let the JVM bind to a random port by omitting the [
addressattribute] (https://docs.oracle.com/cd/E19501-01/819-3664/abgdm/index.html) or by passingaddress=0as command-line arguments. This breaks the process picker because it matches onaddress, which is either missing or its value is0:vscode-java-debug/src/processPicker.ts
Line 9 in 32c57f8
A workaround is to let users manually enter the port: tlaplus/CommunityModules@fa56d3f