Jinbo Wang

We can put it in the insiders first and then see if it affects the performance of project import and features such as code completion.

It's an interesting issue. Are you able to consistently reproduce this issue? What build tool is used to manage the source code? Appreciate if you could provide us with a...

For the first screenshot, it seems that the IntelliSense doesn't work inside some certain lambda expression. This could potentially be a bug, however, we would require a minimal code snippet...

This should be related to enable autobuild support within the Gradle build server, see https://github.com/microsoft/vscode-gradle/issues/1449. // cc: @jdneo

Transfer to the right repo since this issue is related to Java Projects view.

VS Code itself already supports the predefined variables such as `cwd` and `${env:Name}`, see https://code.visualstudio.com/docs/editor/variables-reference#_predefined-variables. I believe the supported environment variable replacement should already exist in your machine's enviroment variable...

The root cause of the issue is that the new Gradle build server from vscode-gradle extension does not support auto build. As a result, it does not inform the Java...

Based on the information provided, I didn't get enough information to analyze the issue. Have you tried using other IDEs to see if the attach debugging works for them?

Since the debugger is using JDI [VirtualMachine#exit(int)](https://docs.oracle.com/en/java/javase/17/docs/api/jdk.jdi/com/sun/jdi/VirtualMachine.html#exit(int)) API to stop the target debuggee, the debugger has little control over this behavior. I'm wondering if other IDEs support the capability you...

the output of extension host process is not related to the debugger extension. Could you describe the exact issue you’re encountering with the debugger extension?