For some time now I’m experiencing SonarQube for IDE creating background tasks for file analysis that just never terminate. This only happens after working a while and I believe it starts mostly when switching branches in Git. The files that are processed seem to be more or less random - nothing that I triggered myself so I am unable to reliably reproduce this. But it happens frequently. I vented my frustration in a review of the plugin and was kindly asked to open a topic here.
While these tasks are running, the plugin has no other functionality and will hang for example when triggered by committing changes. Cancelling the tasks seems to not restore the behavior (still hanging on other tasks).
Only way to restore functionality so far seems to close all open instances of IntelliJ.
Thanks for reporting here. After having a closer look, we found one situation in which the problem can occur. By any chance, do you open the same project in 2 different windows, e.g. from 2 different working copies? We have a bug in supporting this use case, where for example you clone the same repo in 2 different folders, check out different branches and open both projects in IntelliJ. Could you confirm if this is your case? If so, a fix is on the way, and should be released next Monday.
Anyway, thanks for venting on the Marketplace and for helping us improve the product!
It’s not the same constellation for me but maybe related. The projects I am working on are from different repositories but they have a common root project where they were forked from.
I could not yet reproduce it since I enabled the extended logging but will update once I it happens again.
The problem starts to appear if you have 2 projects with a module named the same way, and as soon as you close one of those projects. We will fix this for the next release
It finally happened again and I was able to save the log with ‘Analysis Logs’ and ‘Verbose Output’ enabled.
The log has almost 6000 lines - is there a preferred way to share it?
One thing I noticed in the logs is a call to a search_events endpoint with two project names. The first one is the project were the hanging tasks occurs. The second one is an unrelated project that I’m also working on. Could this cause some issues?
Hey @Hendrik_Iben, we have just released SonarQube for IntelliJ version 10.27. It includes a fix to the problem we mentioned earlier. Could you please update and see if you still notice any issues?
In case a problem occurs, please send us the logs.
The log has almost 6000 lines - is there a preferred way to share it?
If the log is too long to be shared, or if it includes private data that you don’t want to share publicly, I can set up a private upload link. Otherwise, feel free to directly post the log on this thread or via a private message.
One thing I noticed in the logs is a call to a search_events endpoint with two project names. The first one is the project were the hanging tasks occurs. The second one is an unrelated project that I’m also working on. Could this cause some issues?
This very specific call should not cause an issue, but it might be the symptom of an underlying problem. If the problem still happens we will further investigate.
and for helping us improve the product!