Repository navigation
The progress reporter does not stop spinning in the status bar even after the job is completed. #3249
Description
I have been using the 1.22.x pre-release version for daily work and I noticed that sometimes the progress reporter keeps spinning in the status bar even after the job is completed.
As you can see in the screenshot below, the "Initialize Workspace"job has finished and there is no more activity in the “Java Build Status” terminal, but the progress reporter in the status bar is still spinning.
Metadata
Metadata
Assignees
Labels
No labels
Activity
rgrunber commentedon Aug 28, 2023
Is this always reproducible ? Judging by your ~1k warnings / 96 infos that would appear to be JDT-LS loaded :P but I haven't yet reproduced it.
For the past while, any time the status bar was left spinning (with the suspicion that nothing is actually still running), it was some kind of failure above
vscode-java/src/standardLanguageClient.ts
Line 145 in 6cc071a
testforstephen commentedon Aug 29, 2023
It's not consistently reproducible, I observed this behavior a few times in my daily work. BTW, I enabled the setting
"java.showBuildStatusOnStart.enabled": "terminal"in my machine.If I remember correctly, Java extension is supposed to display all progress message in the "Java Build Status" terminal rather than in the status bar. It should be a bug to show progress in the status bar.
And the
activationProgressNotificationis supposed to show as a notification instead of status bar as well.rgrunber commentedon Aug 30, 2023
Found one example of this spinning behaviour (call hierarchy) at eclipse-jdtls/eclipse.jdt.ls#2827 , but haven't looked yet into some of the details of this specific issue.
rgrunber commentedon Sep 6, 2023
Another example of spinning status bar seems to be caused by vscode-java-test through the delegate commands. See eclipse-jdtls/eclipse.jdt.ls#2821 (comment) for details
rgrunber commentedon Sep 25, 2026
I am going to close this based on the solution at eclipse-jdtls/eclipse.jdt.ls#2821 . This should no longer be an issue in the pre-release builds, but feel free to re-open if it is.