Jinbo Wang
Jinbo Wang
> but as far as I can tell, the language server starts up and works as normal. So I don't think we can conclude that this error is always harmful...
In launch mode, the debugger will always force you to compile the code. It's either autobuild or a force compilation before launch. If you wanto to avoid the compilation from...
For 2), It's hard to say what's wrong. It's better to provide a minimum sample project to reproduce the issue. For 3), you can try to add more `-Xmx` memory...
> For 3), currently I use -Xmx2G value (suggested by VSCode on OOM error occured). Not sure if it will fail with OOM or not, need to test it. But...
I couldn't reproduce the issue. Could you share how .classpath file looks like? **F1** -> **Java: Open Java Language Server Log File** -> Navigate the log directory to find the...
I finally reproduced this issue with latest https://github.com/spring-projects/spring-petclinic source code. I observed that **Java Projects** view also listed the `build` directory under "**Project and External Dependencies**" node.  This should...
See https://github.com/spring-projects/spring-petclinic/issues/1213, this seems to be an issue with upstream spring gradle plugin.
When launching the app using the integrated/external terminal, the debugger is only responsible for generating the command line and send it to the terminal to start the app. We do...
Editing the return value is not a supported scenario. The return value is a placeholder variable that's read-only.
> Ok, but possibly an attribute is missing so VSCode doesn't even let you try to modify it. I don't quite remember if readOnly did the trick: https://microsoft.github.io/debug-adapter-protocol/specification#Types_VariablePresentationHint This is...