SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?): No.
And a thorough description of the problem / question:
Stuck on “Getting code actions from ‘SonarQube for IDE’” and the Extension output is cluttered with errors.
Executing c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\jre\21.0.6-win32-x86_64.tar\bin\java -jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\server\sonarlint-ls.jar -stdio -analyzers c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonargo.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonarjava.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonarjavasymbolicexecution.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonarjs.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonarphp.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonarpython.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonarhtml.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonarxml.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonarcfamily.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonartext.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonariac.jar c:\Users\TrueM\.vscode\extensions\sonarsource.sonarlint-vscode-4.16.0-win32-x64\analyzers\sonarlintomnisharp.jar
[Error - 16:20:39.238] Failed to initialize workspace folders.
java.lang.IllegalStateException: Backend service not initialized in time
at org.sonarsource.sonarlint.ls.backend.BackendServiceFacade.getBackendService(BackendServiceFacade.java:116)
at org.sonarsource.sonarlint.ls.folders.WorkspaceFoldersManager.lambda$initialize$1(WorkspaceFoldersManager.java:80)
at org.sonarsource.sonarlint.ls.util.CatchingRunnable.run(CatchingRunnable.java:36)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
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)
[Error - 16:20:39.856] Unable to update configuration.
java.util.concurrent.TimeoutException
at java.base/java.util.concurrent.CompletableFuture.timedGet(Unknown Source)
at java.base/java.util.concurrent.CompletableFuture.get(Unknown Source)
at org.sonarsource.sonarlint.ls.settings.SettingsManager.lambda$didChangeConfiguration$3(SettingsManager.java:185)
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)
[Error - 16:25:39.969] Failed to notify backend on VCS change
java.lang.IllegalStateException: Backend service not initialized in time
at org.sonarsource.sonarlint.ls.backend.BackendServiceFacade.getBackendService(BackendServiceFacade.java:116)
at org.sonarsource.sonarlint.ls.SonarLintLanguageServer.lambda$didLocalBranchNameChange$12(SonarLintLanguageServer.java:640)
at org.sonarsource.sonarlint.ls.util.CatchingRunnable.run(CatchingRunnable.java:36)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
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)
Well, this does not look good Would you mind dropping "sonarlint.trace.server": "verbose", line in your VSCode User Settings JSON file, and sharing the logs with us?
In the original post the logs contained lines like
Failed to initialize workspace folders.
java.lang.IllegalStateException: Backend service not initialized in time
Which would have meant that the initialization failed, and everything else after that would be failing as well. I wanted to see the logs if you would just reload the window and see if the beginning of the logs still contains initialization error.
Or is that part OK now and you are having trouble setting up connection?
Hi @Milli, thanks for coming back to us with logs!
I had a good look at the logs and the problem remains the same - for some reason, the backend service for SonarQube for IDE cannot be initialized in time. Why this happens or how to fix it is impossible to see for now. Would you be able to, please, turn off the "sonarlint.trace.server": "verbose", option from your USER settings and instead simply turn on the verbose logs and share the output again? Hoping this will give us a bit more insight on what is going wrong.
In the meantime, tweaking your editor.codeActionsOnSave setting might help make the failure less noisy (I.e. it should remove the popup progress notification each time you interact with the file).
I am getting the exact same errors, starting with : Failed to initialize workspace folders.
java.lang.IllegalStateException: Backend service not initialized in time
[Debug - 07:54:37.886] Fetching global configuration
[Error - 07:54:45.296] Failed to initialize workspace folders.
java.lang.IllegalStateException: Backend service not initialized in time
at org.sonarsource.sonarlint.ls.backend.BackendServiceFacade.getBackendService(BackendServiceFacade.java:116)
at org.sonarsource.sonarlint.ls.folders.WorkspaceFoldersManager.lambda$initialize$1(WorkspaceFoldersManager.java:80)
at org.sonarsource.sonarlint.ls.util.CatchingRunnable.run(CatchingRunnable.java:36)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
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)
In this case it is for projects that isn’t and shouldn’t be connected to SonarCloud.
Do you know if this started happening from any specific version of SonarQube for IDE? Can you consistently reproduce the issue? And would your setup be considered “particular” for any reason? Such as remote/SSH workspace, very large project, etc. ?
I can’t say when it began, probably this year or late last year.
It is a simple project, with little to no code in it. And there is nothing else particular to it.
However since the extension update yesterday, I haven’t seen it. So it might have been fixed. Before that it was fairly consistent.
As an FYI, we have merged an improvement that changes the order in which things are initialized in SonarQube for IDE, and we are hoping that with this change you should not see the reported errors again.
This will be a part of the next release (v4.19). So once upgraded, please do let us know if the issue keeps re-appearing!!
Would you mind dropping 
Thanks for the logs! 
