Error in SonarLint for IntelliJ 10.4.2 IllegalStateException: There is no ProgressIndicator or Job

SonarQube for IDE IntelliJ Platform
,
1

Environment:

  • Java: JetBrains s.r.o. 17.0.10
  • OS: Windows 10 amd64
  • IDE: IntelliJ IDEA 2024.1
  • SonarLint: 10.4.2.78113
java.lang.IllegalStateException: There is no ProgressIndicator or Job in this thread, the current job is not cancellable.
	at c.ij.oa.progress.CoroutinesKt$runBlockingCancellable$1.invoke(coroutines.kt:128)
	at c.ij.oa.progress.CoroutinesKt$runBlockingCancellable$1.invoke(coroutines.kt:126)
	at c.ij.oa.progress.ContextKt.prepareThreadContext(context.kt:83)
	at c.ij.oa.progress.CoroutinesKt.runBlockingCancellable(coroutines.kt:126)
	at c.ij.oa.progress.CoroutinesKt.runBlockingCancellable(coroutines.kt:121)
	at c.ij.execution.wsl.WslIjentUtil.runProcessBlocking(WslIjentUtil.kt:62)
	at c.ij.execution.wsl.WSLDistribution.lambda$patchCommandLine$2(WSLDistribution.java:239)
	at c.ij.execution.configurations.GeneralCommandLine.createProcess(GeneralCommandLine.java:490)
	at c.ij.execution.configurations.GeneralCommandLine.startProcess(GeneralCommandLine.java:463)
	at c.ij.execution.configurations.GeneralCommandLine.createProcess(GeneralCommandLine.java:356)
	at c.ij.execution.process.OSProcessHandler.startProcess(OSProcessHandler.java:86)
	at c.ij.execution.process.OSProcessHandler.<init>(OSProcessHandler.java:46)
	at c.ij.execution.process.KillableProcessHandler.<init>(KillableProcessHandler.java:41)
	at c.ij.execution.process.KillableProcessHandler.<init>(KillableProcessHandler.java:55)
	at git4idea.commands.GitTextHandler$MyOSProcessHandler.<init>(GitTextHandler.java:146)
	at git4idea.commands.GitLineHandler$1.<init>(GitLineHandler.java:143)
4

Hi @skywalkerAlex ,

Is this the full stack trace?

If not, can you share the full stack trace?
Also, could you provide more detail on what were you doing before you encountered this error?

Thanks

5

Environment:

  • Java: JetBrains s.r.o. 17.0.10
  • OS: Windows 11 amd64
  • IDE: PhpStorm 2024.1
  • SonarLint: 10.4.2.78113
java.lang.IllegalStateException: There is no ProgressIndicator or Job in this thread, the current job is not cancellable.
	at c.ij.oa.progress.CoroutinesKt$runBlockingCancellable$1.invoke(coroutines.kt:128)
	at c.ij.oa.progress.CoroutinesKt$runBlockingCancellable$1.invoke(coroutines.kt:126)
	at c.ij.oa.progress.ContextKt.prepareThreadContext(context.kt:83)
	at c.ij.oa.progress.CoroutinesKt.runBlockingCancellable(coroutines.kt:126)
	at c.ij.oa.progress.CoroutinesKt.runBlockingCancellable(coroutines.kt:121)
	at c.ij.execution.wsl.WslIjentUtil.runProcessBlocking(WslIjentUtil.kt:62)
	at c.ij.execution.wsl.WSLDistribution.lambda$patchCommandLine$2(WSLDistribution.java:239)
	at c.ij.execution.configurations.GeneralCommandLine.createProcess(GeneralCommandLine.java:490)
	at c.ij.execution.configurations.GeneralCommandLine.startProcess(GeneralCommandLine.java:463)
	at c.ij.execution.configurations.GeneralCommandLine.createProcess(GeneralCommandLine.java:356)
	at c.ij.execution.process.OSProcessHandler.startProcess(OSProcessHandler.java:86)
	at c.ij.execution.process.OSProcessHandler.<init>(OSProcessHandler.java:46)
	at c.ij.execution.process.KillableProcessHandler.<init>(KillableProcessHandler.java:41)
	at c.ij.execution.process.KillableProcessHandler.<init>(KillableProcessHandler.java:55)
	at git4idea.commands.GitTextHandler$MyOSProcessHandler.<init>(GitTextHandler.java:146)
	at git4idea.commands.GitLineHandler$1.<init>(GitLineHandler.java:143)
6

Yes, that’s the full stack trace produced from IntelliJ.
SonarLint rules run uppon save of a file, so i cannot locate the source of the issue.

Thanks.

7

Since IntelliJ 2024.1, it seems this issue is raised on background tasks with no ProgressIndicator or Job.

We created this ticket on our side to monitor the progress on this topic.

1 Like
10

This seems related to this bug ticket from JetBrains:

https://youtrack.jetbrains.com/issue/IJPL-148354/WSL-GitLogUtil-There-is-no-ProgressIndicator-or-Job-in-this-thread-the-current-job-is-not-cancellable.

As I understand, it should not impact the user experience, quoting from their developer:

firstly, it’s just a loud error message, but it doesn’t break any production logic. However, it can break tests. We’re working on a way to mitigate the problem with tests.

I believe this is an issue on their side and I would simply ignore it for now.

1 Like