microsoft / microsoft/vscode-java-debug
java.debug.settings.hotCodeReplace "auto" has a wierd behaviour
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 591
- Forks
- 429
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 19
Description
As per title if I set java.debug.settings.hotCodeReplace to "auto" it seems to trigger the "applying code changes" multiple time, which requires more time and eventually ends up in rebuilding the entire application instead of the single modified.
I tried to look out for some kind of output or log to get core of the issue but without any success. I also tried to look out at the docs in case I messed up the settings but nothing looks out of place, except maybe for the "java.autobuild.enabled" set to true (which is not a debugger setting).
"java.debug.settings.console": "internalConsole",
"java.debug.settings.hotCodeReplace": "manual",
"java.debug.settings.forceBuildBeforeLaunch": true
Manually invoking the hot code replace works as intended (at least per my knowledge).
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
Reproduce the issue in the Java debugger with java.debug.settings.hotCodeReplace set to "auto", java.autobuild.enabled true, and forceBuildBeforeLaunch enabled. Compare the repeated "applying code changes" behavior and full rebuild with manual hot code replace; done means automatic replacement no longer repeats unnecessarily or rebuilds the entire application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100