SonarQube for IntelliJ plugin version: until (at least) 11.6.0 to (latest when writing): 11.12.0.84088
IntelliJ version: 2025.3.2
Programming language you’re coding in: Java, TypeScript
Is connected mode used:
SonarQube Server: Enterprise Edition - 9.9.8
A thorough description of the problem:
The problem is the (almost) exact same as the one explained in my previous post: Git inner files are locked.
The main difference is that is is triggered when amending a commit and chaining the gc command after. i.e. git commit --amend --not-edit && git gc --aggressive --prune=now
(Note: I recommend to make an effective file change in the amend to see the problem)
Then what I’m asking is:
a correction (once again)
an anti-regression test verifying that the files are not locked by the plugin (I understand that you want to read them).
Your version is past EOL. You should update to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your update path is:
The error is not based on the server, but on the behaviour of the plugin itself.
I provided the server version, because it’s an asked datum, but it’s clearly not directly related, because, as explained in the 1st ticket, the (forced) shutdown on the JVM running the plugin removes the lock on the Git files…
I identified a potential root cause for this problem, and will provide a fix for our next version. I’ll also ensure it does not happen again - although the issue is not straightforward to reproduce.
We’d still appreciate the logs in case it could help us further investigate, thanks!
About the server version, unfortunately, in cannot do anything about it, I’m just a “small developer in a big society”, and I do not administrate the applications (our Sonar included).
Nicolas: Here are the logs. And thank you for the fix
