-
Notifications
You must be signed in to change notification settings - Fork 323
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
GUI2 times out connecting to Language Server on large projects #9347
Comments
I think the timeout itself is not much a problem; but the retry should properly interpret the 6002 error, and assume that the protocol is initialized. There is however a problem here, namely that we need to know the response of initProtocol, because this is the only source of content roots. We could make sure we handle every response of initProtocol, even if it's for timed out request, but I'm not sure if libraries we use allows that. I think the proper solution is to add an endpoint to language server |
Refinement notes:
|
@farmaazon errors can have a |
Adam Obuchowicz reports a new STANDUP for yesterday (2024-07-18): Progress: Returned for a while to my modification of LS protocol, allowing us to recover from "already initialized" error. Improved solution a bit, fixed tests and documentation. the PR is ready to review; also started the next task of improving look of multiselect drop-down. It should be finished by 2024-07-22. Next Day: Next day I will be working on the #9617 task. Finish new task |
Repro steps
Expected result
No errors
Actual result
Connecting to Language Server times out
Details
Console logs:
localhost-1709807376658.log
WebSocket messages:
Note that the first reply from the backend arrives 17 (!) seconds after the request. This is higher than the 15 second limit, which is demonstrated by the second request being sent after roughly 16 seconds.
Console logs (screenshots):
The text was updated successfully, but these errors were encountered: