-
Notifications
You must be signed in to change notification settings - Fork 137
lsp-ui-sideline--push-info wrong-type-argument arrayp nil #282
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
Comments
It seems like python language server is returning textDocument/hover response which is unhandled. Can you turn on logging via lsp-print-io and post the content of the buffer starting with *lsp-log |
Also, until the issue is fixed you may disable the sideline via lsp-ui-sideline-enable and you may ask about the issue with |
@yyoncho The immediate logs after getting the error are pasted below. Is
|
@tejas-kale it is ms python ls bug and lsp-ui not being defensive enough. As per spec the value property is mandatory in "contents" - check https://microsoft.github.io/language-server-protocol/specification#textDocument_hover |
@yyoncho Thanks for pointing out the cause. So I changed line 214 of
to
After making the change, the |
Yes, if it looks good in the sideline(e. g. no empty lines). Also, we need to test whether the rest of the stuff works fine(e. g. |
|
no elisp knowledge is needed, using lsp-mode and observing whether there are other errors is sufficient.
report language server bug for not following the spec. |
Thanks, @yyoncho. I will observe the change for errors. I have also reported the bug to the language server. |
This should have been fixed, the logic is moved into lsp-mode and it handles that case. Please reopen if you still see it. |
Hi,
I'm using the
Microsoft Python Language Server
withlsp-mode-20190430.945
andlsp-ui-20190428.1045
on Emacs v26.2 on macOS Mojave (10.14.4). Also, I usepython-pylint
as the default checker as thelsp-ui
checker seems to fail with theunresolved import...
error. While either navigating or writing code, the following error keeps popping up every few seconds:My
lsp
configuration looks as follows:Any idea how I can overcome this issue? Let me know what further information you might require for debugging this issue.
The text was updated successfully, but these errors were encountered: