Issues are not shown in sonarqube view nor in the code editor panel

SonarQube for IDE VS Code
1

Please provide

  • Operating system:MacOS Sequoia 15.7.1
  • SonarQube for VS Code plugin version: 4.34.0
  • Programming language you’re coding in: JavaScript
  • Node executable version: 22.11.0
  • Is connected mode used: YES
    • SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?):
    • SonarQube Server Community Edition v9.9.8 (build 100196)

And a thorough description of the problem / question:

Although being able to connect to the server for server side rules and analyzing local files that I open, the issues aren’t shown on the code editor panel or in the sonarqube tab.

The only way I know that the extension works is by going to the output tab and selecting sonarqube for IDE filter from it. After selecting this filter, if I make changes a new analysis is triggered and I can see the number of issues change every time I make some deliberate mistake. However I don’t have any method on to know which line triggers which rule.

A few months back I was using the same setup (but with different IDE and extension versions) and the issues would light up on both code editor panel (the lines which were affected) and also the problems tab.

I have also included the verbose log from IDE startup.

I have tried changing node executable versions, changing to a few older extension versions, deleting and setting up the server connection again but it didn’t work.

Any help would be welcome,
Thank you,

image
image2170×1528 242 KB

SonarQube for IDE.log (61.7 KB)

image
image2164×1600 481 KB

2

Hey @Ufuk_Deniz , welcome to Sonar Community! :waving_hand: :sonar:

Your logs suggest something has gone wrong with SonarQube for IDE issue storage :eyes: Could you try following these troubleshooting steps?

The good news is we are currently working on replacing our existing issue storage technology, so hopefully such issues will not happen anymore! :grin:

Hope this helps,
Sophio

3

Hey Sophio! thanks for the amazingly quick reply :slightly_smiling_face:

I have tried those steps as well before, and now did it again. Unfortunately the problem still persists. There are some .sonarlinttmp and known-findings folders under .sonarlint/work should I delete them as well?

image
image1320×808 174 KB

image
image1310×496 39 KB

image
image1312×496 40.8 KB

4

Hi @Ufuk_Deniz ,

Yes please. Close all running IDE instances (that have SonarQube for IDE running), delete the folders, and reopen the IDE. :clown_face:

Actually, there might be a mistake in the docs - it should say ~/.sonarlint/work/known-findings-store-* :eyes: :see_no_evil_monkey: Will get it fixed!

Please let me know how it goes!

Best,
Sophio

5

Hey Sophio :waving_hand: I hope you’ve had a nice weekend! Good to hear from you again!

I’ve closed my IDE, deleted the folders, emptied the trashcan and opened the IDE again. Unfortunately the issue is a stubborn one, kinda like me :smiley:

I’ve uploaded the new logs in case they might be of help.
I’m eagerly waiting for your instructions :slight_smile:

SonarQube for IDE.log (72.9 KB)

1 Like
6

Hey again Sophio!

I told you I was stubborn :slight_smile:

I don’t know exactly how I fixed this, but I uninstalled then deleted all sonarqube for IDE settings, and all .sonarlint folder, reinstalled an older version, connected it to the server from scratch, updated the extension and here it works now :smiley:

Anyway thanks for the help :clap:

image
image2176×1638 301 KB

1 Like
7

Whoah!! It’s good to hear the issue is resolved :star_struck:

And please be assured that we do not expect users to have to do this anytime they face an issue :melting_face: :joy: We are working hard to improve the experience. So your feedback is very appreciated.

Thanks for taking the time to report this. :wrapped_gift:

All the best,
Sophio

2 Likes
8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.