We’ve noticed some issues are already resolved and no longer flagged as issues by local sonarlint report but still show up in the sonarqube website. Can you please let us know what was the issue ?
Hi,
This is a little light on details.
Have you checked in the changes and re-analyzed?
What versions of SonarQube and SonarLint are we talking about?
Ann
Yes we have checked in the changes and reanalyzed. We are using Community Edition
- v9.9.6 (build 92038) and sonarlint version 10.1.0
Please let me know for further details.
Hi,
What rules are we talking about? Also, what IDE are you using? (Sorry, I should have asked that initially.) If it’s IntelliJ, the current version of SonarLint for IntelliJ is 10.8.1.79205, so with 10.1.0 you would be behind by quite a bit and that could easily explain a divergence.
Ann
We are using STS version 4.20.1 and the rule we are talking about is java:S1166
HI @ganncamp Can you please help us on the above issue
Hi,
I see that STS is an Eclipse derivative. The current version of SonarLint for Eclipse is 10.6.0.82217.
Can you upgrade and see if this is still replicable?
Thx,
Ann
@ganncamp upgraded to the latest one(10.6.0.82217), however, still issue does not match sonarqube website. it looks like sonarlint can detect the fix of code change ,however, sonarqube cannot detect.
Sonarlint shows the change is applied and issue is eliminated while sonarqube still flag the issue.
Hi,
Could we have screenshots of the issue / non-issue on both sides, redacted as necessary, please?
Thx,
Ann