Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid repeatedly setting busy and ready for language server status #2494

Merged
merged 2 commits into from
Jun 10, 2022

Conversation

CsCherrYY
Copy link
Contributor

fix #2493 , for frequently invoking of setBusy().

cc: @Eskibear

Signed-off-by: Shi Chen <chenshi@microsoft.com>
Copy link
Member

@rgrunber rgrunber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems reasonable. I can also see the flickering behaviour.

Logging the notifications when importing a maven project, I noticed many Busy and Ready notifications. In particular I saw some instances where Ready is sent even though it is already set. Can you confirm this as well. Might be worth doing the same for setReady.

@CsCherrYY
Copy link
Contributor Author

I can also observe this via printing the notifications received.

image

multiple setBusy()s and setReady()s will be called when importing Gradle version of spring-petclinic. Let's add the same logic for setReady and move the guard to the ServerStatusItemFactory.

Signed-off-by: Shi Chen <chenshi@microsoft.com>
@CsCherrYY CsCherrYY changed the title Avoid repeatedly setting busy language server status Avoid repeatedly setting busy and ready for language server status Jun 10, 2022
@testforstephen testforstephen added this to the End June 2022 milestone Jun 10, 2022
@testforstephen testforstephen merged commit 4d954f7 into redhat-developer:master Jun 10, 2022
@CsCherrYY CsCherrYY deleted the cs-status-busy branch June 13, 2022 02:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

language status item keeps refreshing
3 participants