Error in SonarLint for IntelliJ-2022.3.2

Environment:

  • Java: JetBrains s.r.o. 17.0.5
  • OS: Windows 10 amd64
  • IDE: IntelliJ IDEA 2022.3.2
  • SonarLint: 8.0.0.63273
java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
	at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:64)
	at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckIndex(Preconditions.java:70)
	at java.base/jdk.internal.util.Preconditions.checkIndex(Preconditions.java:266)
	at java.base/java.util.Objects.checkIndex(Objects.java:359)
	at java.base/java.util.ArrayList.get(ArrayList.java:427)
	at o.sl.ij.editor.EditorDecorator.highlight(EditorDecorator.kt:84)
	at o.sl.ij.ui.tree.TaintVulnerabilityTree.highlightInEditor(TaintVulnerabilityTree.kt:126)
	at o.sl.ij.ui.tree.TaintVulnerabilityTree.showInEditor(TaintVulnerabilityTree.kt:99)
	at o.sl.ij.ui.tree.TaintVulnerabilityTree._init_$lambda$2(TaintVulnerabilityTree.kt:87)
	at c.ij.util.EditSourceOnDoubleClickHandler$TreeMouseListener.processDoubleClick(EditSourceOnDoubleClickHandler.java:173)
	at c.ij.util.EditSourceOnDoubleClickHandler$TreeMouseListener.onDoubleClick(EditSourceOnDoubleClickHandler.java:166)
	at c.ij.ui.DoubleClickListener.onClick(DoubleClickListener.java:30)
	at c.ij.ui.ClickListener$1.mouseReleased(ClickListener.java:59)
	at java.desktop/java.awt.AWTEventMulticaster.mouseReleased(AWTEventMulticaster.java:298)
	at java.desktop/java.awt.Component.processMouseEvent(Component.java:6648)
	at java.desktop/javax.swing.JComponent.processMouseEvent(JComponent.java:3392)
	at c.ij.ui.treeStructure.Tree.processMouseEvent(Tree.java:424)

In the end, we deactivated this useless plugin, as it does not work and causes a continuous error here on all company machines and no help was received to solve it.
I don’t recommend it to anyone.

Hello @Attila_Rivnyak,

That’s unfortunate :confused:

I suppose you are connected to SonarQube. Would you mind sharing more details with us ? Could you try to comment out some portions of the file you are editing to see which one leads to this error ? And if the issue is correctly raised on SonarQube, could you tell me which rule it is ?

Thanks