Error in SonarLint for PHPStorm 2023.2.1

SonarQube for IDE IntelliJ Platform
,
1

Environment:

  • Java: JetBrains s.r.o. 17.0.8
  • OS: Windows 11 amd64
  • IDE: PhpStorm 2023.2.1
  • SonarLint: 9.0.0.75308

*** exception class was changed or removed

  Exception thrown by subscriber method handleEvent(o.ss.sl.core.event.ConfigurationScopeRemovedEvent) on subscriber o.ss.sl.core.websocket.WebSocketService@3276495b when dispatching event: o.ss.sl.core.event.ConfigurationScopeRemovedEvent@48dc22a5
  
  java.lang.NullPointerException: Cannot invoke "o.ss.sl.core.websocket.SonarCloudWebSocket.unsubscribe(String)" because "this.sonarCloudWebSocket" is null
at o.ss.sl.core.websocket.WebSocketService.forget(WebSocketService.java:260)
at o.ss.sl.core.websocket.WebSocketService.handleEvent(WebSocketService.java:101)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:85)
at com.google.common.eventbus.Subscriber$SynchronizedSubscriber.invokeSubscriberMethod(Subscriber.java:142)
at com.google.common.eventbus.Subscriber.lambda$dispatchEvent$0(Subscriber.java:71)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
4

Hello @fernando2amigos,

Thanks for reporting here. Could you provide more details about when this error occurred?

5

Hi @Damien_Urruty

Unfortunately not sure but I believe I just updated local storage from the SonarCloud project and after closing the project settings’ modal that error came in.

6

Hello @fernando2amigos,

I managed to reproduce the issue and I fixed it.

The issue does not have any impact on the SonarLint functionality, so for future readers, you can simply ignore the error.

The fix will be published in our next release planned at the end of this month.

Thanks again for the report

1 Like
8

Good news! :tada:
Glad you managed to preproduce it with such little info :confused:

Thanks!