I still think Sonar should support the code actions on save setting. I want automatic analysis, but I don’t want Sonar to delay auto-saving when I switch focus away from VS Code.
Edit: Actually, even with automatic analysis turned off, the extension causes saving to be delayed indefinitely.
Thanks for reporting this issue. It’s been a long time we did not hear about it, and it is one of those issues that is extremely hard to reproduce (so far I have not been able to do it )
So please, if possible, share with us the logs & thread dumps from the point when you experience saving delays due to SonarQube for IDE Code Actions computation. Please make sure to include logs from the very beginning of the IDE startup. It should start like Executing /Library/Java/JavaVirtualMachines/jdk-17.jdk/Contents/Home/bin/java -jar ...
Welp, I’m back. This issue still happens for me consistently. For a while I just disabled the extension to work around it. Attached are my logs and thread dumps.
This happened a couple of times today. The first log and dumps are from before I enabled verbose output. I also had multiple VS Code windows open. I could not tell which sonarlint-ls.jar process was the right one, so all of them are included. The second log and dumps (those with a “-2” in the name) are from about 10 minutes later, after I had enabled verbose output, closed all the extra VS Code windows, and completely restarted VS Code.
After killing all the sonarlint-ls.jar processes, I restarted the VS Code extension host. Now it is allowing save to complete as expected. Attached are logs.
Thanks to them, we might have found the potential root cause. I still need to properly test the fix though, and verify the root cause. Just to be sure, would you be able to try a custom build with the fix if we provide it?