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 sending an "empty" (lacking project data) startup event. #3655

Merged
merged 1 commit into from
May 29, 2024

Conversation

rgrunber
Copy link
Member

  • When the language server import takes too long (>60s), an "empty" startup event is sent to at least capture some data. This can result in duplicate events when a project import finally completes, or a (now) useless event if something goes wrong.
  • Avoid sending such events as there are better ways to determine if the language server encountered an error

@rgrunber rgrunber requested a review from fbricon May 16, 2024 15:10
@rgrunber rgrunber added this to the End May 2024 milestone May 29, 2024
- When the language server import takes too long (>60s), an "empty"
  startup event is sent to at least capture some data. This can result
  in duplicate events when a project import finally completes, or a
  (now) useless event if something goes wrong.
- Avoid sending such events as there are better ways to determine if the
  language server encountered an error

Signed-off-by: Roland Grunberg <rgrunber@redhat.com>
@rgrunber rgrunber merged commit d369638 into redhat-developer:master May 29, 2024
2 checks passed
@rgrunber rgrunber deleted the remove-empty-startup branch May 29, 2024 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🏗 In progress
Development

Successfully merging this pull request may close these issues.

None yet

1 participant