Troubleshooting

Knowing where to begin looking for information is the first step to reaching out for help. Many answers to commonly found problems can be found on the SonarLint channel of Sonar Community Forum. See below for the basic steps to access the SonarLint logs when analyses results are not what you expected.

How to get SonarLint logs

• Open the SonarLint tool window: View > Tool Windows > SonarLint.
• Enable the Analysis logs and Verbose output in the tool window settings.
• Find the logs in the Log tab of the tool window.

How to access thread dumps

In some cases, it can be useful to extract thread dumps from the running instance of IntelliJ for debugging; thread dumps can help us investigate UI freeze issues or threading problems. This article from JetBrains will help you find or generate those dumps.

If the UI is still reactive, you have another alternative: select Help > Collect Logs and Diagnostic Data to create a .zip file containing one or several threadDumps-XXX folders. In these folders, you should find one .txt file with the current date and time that will contain the logs.

FAQ

I have configured some SonarScanner properties. Are they applied to SonarLint?

No. Scanner properties you may have defined in the sonar-project.properties or pom.xml files (for example sonar.sources or sonar.projectBasedir) only make sense when using the SonarScanner in the command line. SonarLint tries to use IDE metadata to avoid other configurations. 

If you want to share some configuration between SonarScanners and SonarLint, like File exclusions, or some specific analyzer properties, the best way is to use Connected Mode and set the configuration in the SonarQube or SonarCloud UI.

My JS/TS analysis won't run

As reported in this Sonar Community forum thread, the analysis can fail to restart when your computer goes to sleep while analyzing JavaScript or TypeScript files with SonarLint for IntelliJ.

• To solve the issue, simply restart IntelliJ and reopen your project.
• To check if this is the problem, enable the Analysis logs and Verbose output in the tool window settings and re-trigger an analysis; then look for the Skipping the start of the bridge server [...] error notice.