-
Notifications
You must be signed in to change notification settings - Fork 55
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
Could not get trigger characters due to timeout after 50 milliseconds #993
Comments
Hi @kohlschuetter , the logging of this warnings is the normal behavior if the language server is not fast enough to respond in the expected timeframe (50 and 300ms). What would you expect otherwise LSP4E to do, other than logging the problem, if the server does not respond? Regards |
Thanks for looking into this, @rubenporras! How exactly actionable is this message? Imagine you have a very slow system, and LSP4E always responds outside the expected timeframes. What gives? Does it still respond, or is the action discarded? If all we do is to fill the logs / the Error Log view with these messages, then we just make everything even slower. Or just more noisy (the Error Log view is usually empty for me, so this message just stood out) In my case, I believe these errors showed up after resuming from a longer device sleep, so a different problem. Well, if the delay is not in the order of milliseconds but minutes, again, what gives? I think that such conditions should be logged via incrementing counter and then be coalesced separately (for some kind of telemetry), if logged at all. |
I don't think it's considered normal. The language server is expected to report promptly. When it's not the case, it can be perceived as a bug.
It's not LSP4E that responds, but the language server. Most of them are fast enough.
Improving how things are logged would be welcome. What we want is that 1. curious users notice, interpret and report it as a bug of the underlying language server while 2. not breaking other bits of their workflow. Under those conditions, any improvement is welcome. |
Without a reproducible code fragment at hand, it would be helpful to log the actual delay encountered when throwing/logging this exception. These are really two different cases if the timeout is minutes versus milliseconds. |
Seen about 14 times in the log
Could not get trigger characters due to timeout after 50 milliseconds
along with
Could get code actions due to timeout after 300 milliseconds in
textDocument/codeAction
The text was updated successfully, but these errors were encountered: