Problems with vscode extension 4.9.1

Please provide

  • Operating system: Windows 10 22H2, remote ssh to CentOS 7.7
  • SonarLint plugin version: 4.9.1
  • Programming language you’re coding in: C++
  • Is connected mode used: No
    • Connected to SonarCloud or SonarQube (and which version):

And a thorough description of the problem / question:
Hi, after updating to sonarlint vscode extension 4.9.1 I noticed some problems:

  1. sonarlint squiggles not visible in editor
  2. sonarlint sidebar is empty, no Rules visible
  3. “Analyzing 1 file” and spinning thing permanently displayed in status bar

When I check the output i can see this exception:

[Error - 09:53:37.817] Error when handling a notification
[Error - 09:53:37.818] java.lang.IllegalStateException: Duplicate key ba74ba5b-541c-405d-897b-2b7522afe137 (attempted merging values org.sonarsource.sonarlint.ls.connected.DelegatingIssue@6bfba173 and org.sonarsource.sonarlint.ls.connected.DelegatingIssue@5114d7d8)
	at java.base/java.util.stream.Collectors.duplicateKeyException(Unknown Source)
	at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Unknown Source)
	at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(Unknown Source)
	at java.base/java.util.AbstractList$RandomAccessSpliterator.forEachRemaining(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.copyInto(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown Source)
	at java.base/java.util.stream.AbstractPipeline.evaluate(Unknown Source)
	at java.base/java.util.stream.ReferencePipeline.collect(Unknown Source)
	at org.sonarsource.sonarlint.ls.IssuesCache.lambda$reportIssues$3(IssuesCache.java:50)
	at java.base/java.util.HashMap.forEach(Unknown Source)
	at org.sonarsource.sonarlint.ls.IssuesCache.reportIssues(IssuesCache.java:45)
	at org.sonarsource.sonarlint.ls.AnalysisHelper.handleIssues(AnalysisHelper.java:102)
	at org.sonarsource.sonarlint.ls.clientapi.SonarLintVSCodeClient.raiseIssues(SonarLintVSCodeClient.java:664)
	at org.sonarsource.sonarlint.core.rpc.client.SonarLintRpcClientImpl.lambda$raiseIssues$35(SonarLintRpcClientImpl.java:368)
	at org.sonarsource.sonarlint.core.rpc.client.SonarLintRpcClientImpl.lambda$notify$4(SonarLintRpcClientImpl.java:150)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

When I rolled back to previous version (4…8.0) the problems don’t happen

Any idea what might be causing this?

Seeing the same long analysis times and blast of Java duplicate key exceptions with versions 4.9.1 and 4.10.0 of the SonarLint extension under Linux vscode 1.85.2, while developing C++ in a devcontainer and connected to SonarQube EE v10.5.1 (90531).

Rolling back to 4.8.0 seems to be the workaround for now.

Any chance of an official fix for this?

Hello, welcome to the community! And thanks for reporting this behavior.

Could you please share the full SonarLint Output between when you start the IDE and when the exception occurs?

This behavior is very hard to reproduce, and with only the exception it’s virtually impossible to investigate. Help us help you :slight_smile:

It looks like this may have been fixed in 4.11.1 by way of update to sonarlint-language-server 3.11.1. @Tim1 how’s it looking for you?

BenS: yep, 4.11.1 looks good, all working OK now. Thanks!

(BenS, sorry I can’t tag you in this comment I got some error about “new users can’t mention other users”)

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