You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the integration with Eclipse IDE, in automated tests (when things go crazy fast), we're hit by the fact that the Omnisharp-Roslyn language server sends initilized too early without being ready to handle requests.
The symptom is that we wait to receive initialized before sending other requests, but if we send them just after, those requests seem ignored.
This sequence of messages is the hint I take to conclude (maybe erroneously) that initialized is sent too early
As you can see the {"protocolVersion":"2.0","method":"window/logMessage","params":{"type":4,"message":"initialized..."}} comes later while the client (according to the spec) expect initialization to be complete after 1st response.
For some operations like documentChange, it makes that messages can be sent between the declared readiness and the actual readiness, making the server ignore those messages and building an erroneous state of the document.
The text was updated successfully, but these errors were encountered:
In the integration with Eclipse IDE, in automated tests (when things go crazy fast), we're hit by the fact that the Omnisharp-Roslyn language server sends initilized too early without being ready to handle requests.
The symptom is that we wait to receive
initialized
before sending other requests, but if we send them just after, those requests seem ignored.This sequence of messages is the hint I take to conclude (maybe erroneously) that initialized is sent too early
As you can see the
{"protocolVersion":"2.0","method":"window/logMessage","params":{"type":4,"message":"initialized..."}}
comes later while the client (according to the spec) expect initialization to be complete after 1st response.For some operations like documentChange, it makes that messages can be sent between the declared readiness and the actual readiness, making the server ignore those messages and building an erroneous state of the document.
The text was updated successfully, but these errors were encountered: