You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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 activationProgressNotification is supposed to show as a notification instead of status bar as well.
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.
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.
The text was updated successfully, but these errors were encountered: