Programming language you’re coding in: Java, Scala
Is connected mode used: No
Connected to SonarCloud or SonarQube (and which version):
While performing analysis for all the project files it is analyzing the file and also generating the report but the report stays for only 1 or 2 seconds, and then it disappears. And the following message shows: No new issues from last 30 days
It is working fine for the Analyze VCS Changed Files.
The log for the following is attached. ErrorLog.txt (276.7 KB)
Hello @SnehasishChar, I believe you have the settings “Focus on new code” enabled, which means we only show you the most recent issues first. However, you should be able to see older issues in a list that is minimized by default:
After expanding the older issues:
Could you confirm that you have the same behavior? If not, could you provide a screenshot of what you see? I do not see anything suspicious on the logs.
Could you also explain how you triggered the analysis?
Are you triggering the analysis of all files via the Analyze All Project Files in the report view or by another means?
Looking at the logs, it seems that another analysis was triggered very shortly after the analysis of all the files. I am unaware of such issues. Would it be possible that you triggered another analysis unintentionally?
Are these two files corresponding to anything specific in your repository?
/project/plugins.sbt
/project/build.properties
They do not seem included in the analysis of the whole project.
The analysis is working fine for the whole project, and issues are found, but it gets hidden by the new analysis triggered right after on two files. This is a really strange behavior.
Do you have multiple IDEs or projects opened at the same time?
Could you also try analyzing the whole project by selecting the root folder and pressing Ctrl+Shift+S or by right-clicking the folder and selecting SonarLint → Analyze with SonarLint and seeing if the behavior is the same?
If I have single project open or multiple project opened it does not matter in both the scenario the behaviour is same.
As long as triggering by selecting the root folder it is the same behaviour. But if I analyze a particular folder then it works fine. Else same it showing for some milisecond and then disappear.
I think after completing the whole project analysis it again alayzing the plugins.sbt and build.properties as a project. That is the reason for over riding the report.
We are facing the same behavior but using the “Analyze VCS Changed Files” button. It seems another analysis is triggered after the first analysis, which wipes out the results from the first analysis. Can I provide the log output to you privately? It contains sensitive information.
Hello @mkomko, you should be able to message me directly on the forum by clicking on my profile. The logs won’t be accessible to anyone else, and I won’t share them publicly.
Good idea, but sadly I don’t see any functionality to message you or to read messages for that matter. I don’t know if it’s not available to me as a relatively new user or not available at all.
