References to launch.json in error messaging may be misleading
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start with the repository search for launch.json linked in the issue and inspect the two error-message references. Determine wording that does not imply this repository reads a launch.json file; done means the misleading references are clarified or removed for debugger sessions started through the VS Code debug API.
Written by the indexing model from the issue text.
Description
https://github.com/microsoft/java-debug/search?q=launch.json
There appear to be only two references to launch.json in this repository. There does not appear to be any part of the code actually reading or referencing or introspecting a file named launch.json.
End users may find references to launch.json confusing if a third party tool has launched the debugger to connect to a java process and did not pass in a "projectName" to the call. While I realize this is a bit outside the scope of this repository, an example would be a vscode extension using the vscode.debug API (which flows to the https://github.com/microsoft/vscode-java-debug extension) and not setting a project name. In this case there is no launch.json file.
private async startDebugger(port: string) {
this.port = port;
vscode.debug.startDebugging(undefined, {
type: 'java',
request: 'attach',
name: 'Debug (Remote)',
hostName: 'localhost',
port,
projectName // set to undefined as an example
});
}
Since this repository itself does not read a launch.json at all, and all configuration is passed in via a Debug Adapter, not an existing file, these references to a file name are very misleading.
- Dominant language
- Java
- Stars
- 409
- Forks
- 204
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
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/java-debug
-
ai-triaged bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/java-debug#611 · 2 comments ·
-
ai-triaged enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/java-debug#608 · 3 comments ·
-
ai-triaged question
Difficulty 5/5 Over a week Newbie friendliness 30/100
microsoft/java-debug#597 · 1 comment ·
-
ai-triaged bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/java-debug#588 · 1 comment ·
-
ai-triaged question
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
microsoft/java-debug#582 · 1 comment ·
All issues in microsoft/java-debug
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
enhancement Tools
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
apache/rocketmq-dashboard#5008 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
DETECT_PARAMETER_NAMES=false silently disables @ConstructorProperties-based Creator detection too Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FasterXML/jackson-databind#6229 ·