microsoft / microsoft/vscode-java-debug

Add option to disable no-config debugging

Open
#1,689 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-triaged enhancement
Dominant language
TypeScript
Stars
591
Forks
429
Avg merge
1d 9h
Merged PRs (30d)
19

Description

The way no-config debugging is handled produces issues on certain linux distributions, like NixOS, making the extension unusable.

In the particular issue I'm experiencing, the extension fails to generate a directory:

2026-09-06 15:40:43.556 [error] Activating extension vscjava.vscode-java-debug failed due to an error:
2026-09-06 15:40:43.556 [error] Error: ENOENT: no such file or directory, mkdir '/home/USER/.vscode-oss/extensions/vscjava.vscode-java-debug/.noConfigDebugAdapterEndpoints'
	at Object.mkdirSync (node:fs:1350:26)
	at /nix/store/2adnr1in2fxpjmdbwyp6gjawily2wy4x-vscode-extension-vscjava-vscode-java-debug-0.59.0/share/vscode/extensions/vscjava.vscode-java-debug/dist/extension.js:2:339586
	at Generator.next (<anonymous>)
	at /nix/store/2adnr1in2fxpjmdbwyp6gjawily2wy4x-vscode-extension-vscjava-vscode-java-debug-0.59.0/share/vscode/extensions/vscjava.vscode-java-debug/dist/extension.js:2:338649
	at new Promise (<anonymous>)
	at r (/nix/store/2adnr1in2fxpjmdbwyp6gjawily2wy4x-vscode-extension-vscjava-vscode-java-debug-0.59.0/share/vscode/extensions/vscjava.vscode-java-debug/dist/extension.js:2:338397)
	at t.registerNoConfigDebug (/nix/store/2adnr1in2fxpjmdbwyp6gjawily2wy4x-vscode-extension-vscjava-vscode-java-debug-0.59.0/share/vscode/extensions/vscjava.vscode-java-debug/dist/extension.js:2:338859)
	at /nix/store/2adnr1in2fxpjmdbwyp6gjawily2wy4x-vscode-extension-vscjava-vscode-java-debug-0.59.0/share/vscode/extensions/vscjava.vscode-java-debug/dist/extension.js:2:296042
	at Generator.next (<anonymous>)
	at a (/nix/store/2adnr1in2fxpjmdbwyp6gjawily2wy4x-vscode-extension-vscjava-vscode-java-debug-0.59.0/share/vscode/extensions/vscjava.vscode-java-debug/dist/extension.js:2:290398)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the source corresponding to registerNoConfigDebug in the extension and trace where no-config debugging is activated. Review the extension's configuration and activation entry points to determine where a disable option belongs. Done means users can turn off no-config debugging and the extension activates successfully on affected Linux distributions.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
devtools
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.