Closed andromedabushturkey closed 2 years ago
@DanTup would you mind checking this lsp log, I don't see anything wrong with the requests coc.nvim
is sending but the requested capabilities seem not to be returned by the dart lsp
@Kavantix are you able to run the server with --instrumentation-log-file=/some/path.txt
to capture a full log (it some additional info to just the request/responses)? Can you also confirm the exact full command being used to spawn the LSP server?
@DanTup thanks for checking, I just found the problem.
Dart changed the output of dart --version
from stderr to stdout which we were using to enable/disable dynamic capability registration for dart above 2.6
@andromedabushturkey 1.9.7 should resolve the issue
@Kavantix I'm not sure I understand - the server should behave correctly with or without dynamic capabilities. I also don't think you should need to sniff the version number for anything - I think you should be able to get everything you need from the server capabilities?
I agree @DanTup on both points. The first is a quirk of coc I believe. And the second is probably extremely outdated, I'll try if I can see why @iamcco added that.
Ah it is because of this issue Definitely outdated, might consider removing the version check at some point.
Gents, you guys rock. Huge thank you for your amazing response time. Cheers!!
@andromedabushturkey you're welcome :)
@Kavantix ah, I forgot about that. Though if you disable dynamic registration on the latest version of the server (eg. if you incorrectly assumed it was < 2.6 because of the --version
change), I would still expect the server to function correctly. If that doesn't seem to be the case, please let me know and I'll take a look :-)
Well the problem is that it isn't disabling dynamic registrations per se, coc is just throwing away any registerCapability
requests coming in (the quirk I was talking about)
The server in general was working, just not the capabilities that are dynamically registered.
Ah, gotcha :) FWIW the client didn't send dynamicRegistration: true
then the server would register everything statically (and not send any registerCapability
calls). I don't know enough to know if that's a worthwhile (or even reasonable) change though.
Do let me know if anything comes up that might be related to the server though. I don't know enough to reasonable test all of the clients that are using the LSP server, but I'd very much like to ensure it's as compatible as possible :-)
Hi guys, I'll keep it real short and simple. After updating my Flutter to version 2.8(Stable Channel), I ran into issue #140. I did the same thing as dprophete and llucax in the #140 thread and get the same results. will this require an update or was this fixed in an other way?
Thank you in advance for all the help.
Cheers