IntelliJ error - No issue found with key

Hello @nicolas.quinquenel, im having the same issue but with the latest version of plugin, should i create a new topic?

  • Operating system: Linux Ubuntu 24.04
  • SonarLint plugin version: 10.12.0.79769
  • Programming language you’re coding in: Java
  • Is connected mode used: Yes
  • Connected to SonarQube (and which version): Community Edition v10.6 (92116)
  • IntelliJ IDEA 2024.2.4 Build #IC-242.23726.103
  • JDK: 17.0.9; Vendor: IBM
 [2024-11-11T18:17:11.653] [SonarLint Server RPC request executor] DEBUG sonarlint - GET 200 https://sonarqube.custom.domain.com/api/issues/search.protobuf?issues=41ddf523-66c4-4466-9d12-xxxxxxx&additionalFields=transitions&ps=1&p=1 | response time=193ms
 [2024-11-11T18:17:11.653] [SonarLint Server RPC request executor] ERROR org.eclipse.lsp4j.jsonrpc.RemoteEndpoint - Internal error: org.sonarsource.sonarlint.core.serverapi.exception.UnexpectedBodyException: No issue found with key '41ddf523-66c4-4466-9d12-xxxxxxx'
java.util.concurrent.CompletionException: org.sonarsource.sonarlint.core.serverapi.exception.UnexpectedBodyException: No issue found with key '41ddf523-66c4-4466-9d12-xxxxxxx'
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:315)
	at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:320)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:649)
	at java.base/java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:482)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: org.sonarsource.sonarlint.core.serverapi.exception.UnexpectedBodyException: No issue found with key '41ddf523-66c4-4466-9d12-xxxxxxx'
	at org.sonarsource.sonarlint.core.serverapi.issue.IssueApi.searchByKey(IssueApi.java:247)
	at org.sonarsource.sonarlint.core.issue.IssueService.lambda$checkStatusChangePermitted$5(IssueService.java:199)
	at java.base/java.util.Optional.orElseGet(Optional.java:364)
	at org.sonarsource.sonarlint.core.issue.IssueService.checkStatusChangePermitted(IssueService.java:198)
	at org.sonarsource.sonarlint.core.rpc.impl.IssueRpcServiceDelegate.lambda$checkStatusChangePermitted$3(IssueRpcServiceDelegate.java:68)
	at org.sonarsource.sonarlint.core.rpc.impl.AbstractRpcServiceDelegate.lambda$requestAsync$0(AbstractRpcServiceDelegate.java:67)
	at org.sonarsource.sonarlint.core.rpc.impl.AbstractRpcServiceDelegate.computeWithLogger(AbstractRpcServiceDelegate.java:135)
	at org.sonarsource.sonarlint.core.rpc.impl.AbstractRpcServiceDelegate.lambda$requestAsync$1(AbstractRpcServiceDelegate.java:65)
	at java.base/java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:646)
	... 4 common frames omitted

Error while retrieving the list of allowed statuses for issues
org.eclipse.lsp4j.jsonrpc.ResponseErrorException: Internal error.
	at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleResponse(RemoteEndpoint.java:220)
	at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:204)
	at org.sonarsource.sonarlint.core.rpc.protocol.SingleThreadedMessageConsumer.lambda$new$0(SingleThreadedMessageConsumer.java:51)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:572)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
	at java.base/java.lang.Thread.run(Thread.java:1583)

Hello @NathanAlcantara, thanks for reaching out to us. I have moved your message to a new thread for clarity.

As I understand from the logs, you tried to change the status of an issue. I will ping the relevant team to investigate this, thanks!

2 Likes

Hello @NathanAlcantara ,

I’ve created SLCORE-1045 on our side to investigate the issue.

Is the error you observe raised for one/few specific issue(s) or for all issues?

Hi @vojtech.suchy, i appreciate the investigation!

I cannot “mark as” for all issues that already analyzed for sonarqube, but new ones before analysis yes

Thank you for the update. I’ve updated the investigation ticket with the information.

2 Likes

Hello @NathanAlcantara,

Sorry to come back a bit late on this topic, do you still experience the problem? I cannot reproduce it on my side. If so, could you share a bit more details? Does an issue with this key exist on the server?

As you are using Community Edition, branches are not supported. Is it possible that you still run analysis from different branches? If so, I could imagine that some issues might appear and disappear, as the last analysis will always overwrite the previous one.

Let me know if I can help further