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
The provider completions subsystem requests results from the lsp and nrepl providers sequentially and then merges the results together. If either of these providers fail to report completion items and throws an error then the entire flow fails.
Ideally if one of the providers is working and is able to report results then the completions should continue to work.
I ran into this while dealing with an obscure issue which was causing my nrepl-based completions to fail. This issue isn't reproducible on my setup anymore, however the above problem can be reproduced simply by stopping the LSP server (and leaving the nrepl connected). I would expect completions to continue to work if I have an active nrepl connection but have stopped the LSP.
The fix should be to simply handle provider response failures more gracefully. I have an incoming PR which addresses this.
The text was updated successfully, but these errors were encountered:
The provider completions subsystem requests results from the
lsp
andnrepl
providers sequentially and then merges the results together. If either of these providers fail to report completion items and throws an error then the entire flow fails.Ideally if one of the providers is working and is able to report results then the completions should continue to work.
I ran into this while dealing with an obscure issue which was causing my nrepl-based completions to fail. This issue isn't reproducible on my setup anymore, however the above problem can be reproduced simply by stopping the LSP server (and leaving the nrepl connected). I would expect completions to continue to work if I have an active
nrepl
connection but have stopped the LSP.The fix should be to simply handle provider response failures more gracefully. I have an incoming PR which addresses this.
The text was updated successfully, but these errors were encountered: