Error in SonarLint for IntelliJ (EAP, when creating new branch)

SonarQube for IDE IntelliJ Platform
,
1

Environment:

  • Java: JetBrains s.r.o. 17.0.4.1
  • OS: Mac OS X aarch64
  • IDE: IntelliJ IDEA 2022.3 EAP
  • SonarLint: 7.1.0.54364
o.ss.sl.core.serverconnection.storage.StorageException: Failed to read file: /Users/jonesn/Library/Caches/JetBrains/IntelliJIdea2022.3/sonarlint/storage/736f6e6172636c6f75642d6f647069/projects/6f6470695f656765726961/project_branches.pb
	at o.ss.sl.core.serverconnection.storage.ProtobufUtil.readFile(ProtobufUtil.java:42)
	at o.ss.sl.core.serverconnection.storage.ProjectStorage.lambda$getProjectBranches$3(ProjectStorage.java:73)
	at o.ss.sl.core.serverconnection.storage.RWLock.read(RWLock.java:32)
	at o.ss.sl.core.serverconnection.storage.ProjectStorage.getProjectBranches(ProjectStorage.java:73)
	at o.ss.sl.core.serverconnection.ServerConnection.getProjectBranches(ServerConnection.java:117)
	at o.ss.sl.core.ConnectedSonarLintEngineImpl.getServerBranches(ConnectedSonarLintEngineImpl.java:363)
	at o.sl.ij.vcs.DefaultVcsService.resolveServerBranchName(DefaultVcsService.kt:65)
	at o.sl.ij.vcs.DefaultVcsService.getServerBranchName(DefaultVcsService.kt:53)
	at o.sl.ij.issue.vulnerabilities.TaintVulnerabilitiesLoader.loadServerTaintVulnerabilitiesForFile(TaintVulnerabilitiesLoader.kt:62)
	at o.sl.ij.issue.vulnerabilities.TaintVulnerabilitiesLoader.getLocalTaintVulnerabilitiesForFile(TaintVulnerabilitiesLoader.kt:50)
	at o.sl.ij.issue.vulnerabilities.TaintVulnerabilitiesLoader.getTaintVulnerabilitiesByOpenedFiles(TaintVulnerabilitiesLoader.kt:44)
	at o.sl.ij.issue.vulnerabilities.TaintVulnerabilitiesPresenter$presentTaintVulnerabilitiesForOpenFiles$1.run(TaintVulnerabilitiesPresenter.kt:104)
3

Hello Nigel,

Thanks for reporting this error. I see a situation where this could happen, still I don’t understand what lead you to it. Could you share with us the full logs ? If you restart the IDE does it still happen ?

4

Hello,

We received similar reports, I created this ticket and I am working on a fix for the next release.

Thanks for reporting!

6

This error has been fixed and released, please update to the latest version

8

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