-
Notifications
You must be signed in to change notification settings - Fork 420
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
Upgraded to latest lsp #1562
Upgraded to latest lsp #1562
Conversation
1471c79
to
9539e29
Compare
@david-driscoll I tried the alpha bits yesterday, with no success. Actually it didn’t even initialize using the C# LSP Client (version 0.12.1). Saw another exception too bubble up regarding converting ”empty json rpc response” to a ”initialized response”.. Or something like that. Can look again with this PR instead. |
Seeing this with C# LSP Client when updating Omnisharp to use LSP libs 0.13.0-alpha*
Initialized params is empty, so don't know what happened here. https://microsoft.github.io/language-server-protocol/specification#initialized Will look into this, and also try to fix the issues seen in #1505 and #1525 as these are not fixed yet with updating LSP libs. |
Eagerly awaiting this merge! Was also running into the didChange handler failures. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
How's this coming along? Any blockers? |
Surprised this wasn't included in the last release :( |
I chatted with @mholo65 yesterday and we updated the test from #1583 from Linux since it's unstable on Azure DevOps with the LSP changes in. We can investigate that separately next and it shouldn't hold up this PR, the test still runs on Mac and Windows for now. Should be good to go now. |
@mholo65 This upgrade went pretty well things seem to working.. I dunno if might help with your other issue.