Error in SonarLint for IntelliJ11

SonarLint IntelliJ Platform
,
1

Environment:

  • Java: JetBrains s.r.o. 17.0.7
  • OS: Windows 10 amd64
  • IDE: JetBrains Rider 2023.2 EAP 2
  • SonarLint: 8.2.0.68615
java.lang.Throwable: Slow operations are prohibited on EDT. See SlowOperations.assertSlowOperationsAreAllowed javadoc.
	at c.ij.oa.diagnostic.Logger.error(Logger.java:367)
	at c.ij.util.SlowOperations.assertSlowOperationsAreAllowed(SlowOperations.java:129)
	at c.ij.workspaceModel.core.fileIndex.impl.WorkspaceFileIndexDataImpl.ensureIsUpToDate(WorkspaceFileIndexDataImpl.kt:129)
	at c.ij.workspaceModel.core.fileIndex.impl.WorkspaceFileIndexDataImpl.getFileInfo(WorkspaceFileIndexDataImpl.kt:75)
	at c.ij.workspaceModel.core.fileIndex.impl.WorkspaceFileIndexImpl.getFileInfo(WorkspaceFileIndexImpl.kt:220)
	at c.ij.workspaceModel.core.fileIndex.impl.WorkspaceFileIndexImpl.findFileSetWithCustomData(WorkspaceFileIndexImpl.kt:205)
	at c.ij.oa.roots.impl.ProjectFileIndexImpl.getModuleForFile(ProjectFileIndexImpl.java:88)
	at com.jetbrains.rider.projectView.ideaInterop.RiderProjectFileIndex.getModuleForFile(RiderProjectFileIndex.kt:19)
	at o.sl.ij.util.SonarLintAppUtils.lambda$findModuleForFile$0(SonarLintAppUtils.java:54)
	at c.ij.oa.application.impl.ApplicationImpl.runReadAction(ApplicationImpl.java:921)
	at o.sl.ij.util.SonarLintAppUtils.findModuleForFile(SonarLintAppUtils.java:50)
	at o.sl.ij.util.SonarLintAppUtils.getRelativePathForAnalysis(SonarLintAppUtils.java:78)
	at o.sl.ij.finding.persistence.LiveFindingCache.createKey(LiveFindingCache.java:183)
	at o.sl.ij.finding.persistence.LiveFindingCache.lambda$flushAll$3(LiveFindingCache.java:146)
	at java.base/java.util.LinkedHashMap.forEach(LinkedHashMap.java:721)
3

Hello @sunnamed434,

This problem happens on the EAP version only due to a recent change. I created this ticket and we will try to fix it soon.

Thanks for reporting this!

5

Hi!

Np. What do you think about adding an automatic bug report? Due to not always being possible to stay open a browser, even on a laptop, try to check how Rider does, issue found - click - report - done.

Cuz, it’s boring when you’re coding and the browser opens up, you will get much more reports in that way, I’m sure

6

Thanks for the feedback, it’s something we are discussing. In any case, it’s not part of the near roadmap

7

ok np, at least would be great to make the bug report title with exception info or something like that