SonarLint and Sonarqube Server Community edition issue

SonarQube Server / Community Build
1

Community Build v25.9.0.112764

Deployed through Openshift helm chart

Trying to use visual studio code sonarqube for ide and use connected mode

I did not enable any custom rules it is all default, but I am having discrepancy in the number of findings. The code is in python.

Here are some examples.

image

image
image862×269 23.7 KB

2

In the logs there is no error it is all exit status 200

3

Hi,

Welcome to the community!

I’m not understanding what the discrepancy is. Can you elaborate?

 
Thx,
Ann

4

Hi,

I have 200 security hotspots in my sonarqube server, but in my sonarqube for IDE, it only flag out 100. So there is about a 100 issues not being flagged out

5

Hi,

Can you share the version of SonarQube for IDE you’re using? Can you also share a verbose log from IDE startup to where you’re expecting to see the SecurityHotspots, but don’t?

Off-hand, this sounds like a pagination problem, but let’s see what the logs say.

Also, and for context, SonarQube for IDE is not intended to be a full code inspection tool, but an aide for active coding. The idea is to see issues in the code files you’re currently working in, not to browse all issues.

 
Thx,
Ann

6

SonarQube for IDE.log (10.1 KB)

Hi Ann, thanks for replying.

Here is the logs and I am using SonarQube for IDE v4.34.0

7

Sorry the log was not complete. Here is the full log from start up to scan.

SonarQube for IDE.log (19.0 KB)

8

Here is an example of the differences in findings. As you can see in the IDE there is only 10 results, but in the UI there is 50 results when i do a pysonar scan.

image
image911×291 24.4 KB

image

10

Hi,

Thanks for the log. I’ve flagged this for the team.

 
Ann

12

Hello @yangyang,

Thank you for reporting this issue and providing the logs. I understand it must be confusing to see a discrepancy between the SonarQube server and VS Code, especially with such a large difference (50 issues vs. 10).

While the logs haven’t immediately pinpointed the cause, there are a couple of things we should check:

  • Check “Focus on New Code” in VS Code: In SonarQube for VS Code, please verify your “Focus on New Code” filtering setting. This feature only shows issues in code that has changed since your last SonarQube analysis, which could explain why you see fewer issues locally.
  • Share Failing Rules: To investigate potential configuration or rule compatibility issues, could you please share the details of a few rules that are failing on the server but not appearing in VS Code? Knowing these rules will help us in narrowing down the cause.

We appreciate your help as we work to resolve this!

Kind regards,
Vasilis