Skip to content
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

Constant errors from LSP plugin #26

Closed
gebner opened this issue May 25, 2021 · 4 comments
Closed

Constant errors from LSP plugin #26

gebner opened this issue May 25, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@gebner
Copy link
Collaborator

gebner commented May 25, 2021

When editing a Lean 4 file, I am getting the following kind of error very frequently:

LSP[leanls]: Error NO_RESULT_CALLBACK_FOUND: {
  id = 101,
  jsonrpc = "2.0"
}

Sometimes the response is clearly from autocompletion. Is there something obvious that I should be doing?

@Julian
Copy link
Owner

Julian commented May 25, 2021

I've seen this error before but haven't been able to deterministically reproduce it... For me it's happened at most once per session, and rarely (i.e. not in every session).

I think what it means is the server is sending back some message that isn't registered in vim.lsp.handlers -- so either that's something the server shouldn't be sending or something we can put a null handler in there for, but since I haven't been able to deterministically reproduce I haven't been able to check which -- in fact I don't even know what kind of request is being responded to!

So yeah maybe is there anything you can share that deterministically seems to cause this? I'll try to find the spot that we'd need to instrument to debug which LSP request is involved there, I think if we shove a print statement in there it'd tell us what handler we should add to vim.lsp.handlers, if it's in fact a neovim bug.

@Julian Julian added the bug Something isn't working label May 25, 2021
@gebner
Copy link
Collaborator Author

gebner commented May 30, 2021

leanprover/lean4#499

@Julian
Copy link
Owner

Julian commented May 30, 2021

Nice find.

@Julian
Copy link
Owner

Julian commented Jun 6, 2021

Fixed in leanprover/lean4#506 it seems. Thanks (both for diagnosing and fixing!)

@Julian Julian closed this as completed Jun 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants