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
Stop language server on shutdown (#681) #688
Conversation
I now understand, why there is UPDATE: done by preventing repeating calls to |
Note the use of Plafotm.getLog() - ILog can't be received from plug-in activator during platform shutdown.
The failing Junit test seems to be unstable in master. |
Hi @basilevs, I have realized that this PR has been waiting for 9 months for my review. Sorry for that. Would you still like to merge the PR after resolving the conflicts? I did not look at the conflicts, but might any of the conflicts have resolved the problem you wanted to fix? Regards |
|
But this PR would have tens of version bumps this way? Surely that is impractical? |
Yes, it is not very practical, but it is also not a big deal, and it is so far how the project has handled it. I think the reason is not to bump plugin versions unless there is a code change. |
Well, anyway, a separate PR in this case is important, as it demonstrates, that builds are broken and meaningful changes in other PRs are not the cause. |
Tests are failing. Probably due to merge side-effects. Further work is required.
|
My project using LSP4E is suspended, so I'm dropping this work. |
The problem (#681):
Language server is not stopped on Eclipse shutdown, as LanguageServerWrapper does not call
stop()
before stopping its thread pools.Solution:
stop()
observablestop()
to complete on Eclipse shutdownConcerns:
Test is slow locally - shutdown command times out for no apparent reason
Synchronization fixes may lead to deadlocks.