debug run can only succeed once.

[Mobius0526]

Extension Name: vscode-gradle
Extension Version:3.17.1
OS Version:windows
VSCode version:1.106.2

Describe the bug
When org.gradle.configuration-cache=true is set in gradle.properties, debugging will only start once, and will fail to start on subsequent attempts, remaining in a state of waiting for the debugger to link.

To Reproduce
Generate a template project from https://neoforged.net/mod-generator. After opening the project, execute runClient. This execution will succeed. After closing and executing it again, this time it will pause waiting for the debugger to connect until it times out.

Does the bug still exist if you disable all other extensions?
Yes

Additional context
When org.gradle.configuration-cache=true is set, the port provided is the same every time debugging is started.

[github-actions]

Hi @Mobius0526, 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.

• This is caused by Gradle’s up-to-date checks (and configuration cache) keeping the run task SKIPPED on subsequent launches, so the debug JVM args never get re-injected.

Suggestions:

• Disable configuration cache for your debug launches:

// in .vscode/settings.json
{
  "gradle.arguments": ["--no-configuration-cache"]
}

• Force run to always execute by marking its outputs as never up-to-date. Add to your build.gradle:

tasks.named('run') {
  outputs.upToDateWhen { false }
}

• Or add a clean predecessor so VS Code’s Gradle extension always runs a cleanup step before debugging. In build.gradle:

task cleanRun(type: Delete) {
  delete "build"
}
run.dependsOn cleanRun

Labels:

• bug

duplicateUrls: []

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!