Closed matu3ba closed 1 year ago
You'll need to take it to https://github.com/microsoft/lsprotocol, that's what's reponsible for (de)serialization
I think you need to pip install -U lsprotocol
pip3 install -U --user lsprotocol
Requirement already satisfied: lsprotocol in /home/user/.local/lib/python3.8/site-packages (2023.0.0a1)
Requirement already satisfied: attrs in /home/user/.local/lib/python3.8/site-packages (from lsprotocol) (23.1.0)
Requirement already satisfied: cattrs in /home/user/.local/lib/python3.8/site-packages (from lsprotocol) (23.1.2)
Requirement already satisfied: exceptiongroup in /home/user/.local/lib/python3.8/site-packages (from cattrs->lsprotocol
) (1.1.1)
Requirement already satisfied: typing_extensions>=4.1.0 in /home/user/.local/lib/python3.8/site-packages (from cattrs->
lsprotocol) (4.6.3)
I think its a general problem with generics, as they are hard to resolve. For example, in C++ clangd is also unable to show the context in (simple) overloaded functions and gives up after the first argument.
However, clangd does not show annoying errors.
This has nothing to do with generics and even less to do with clangd. It is a deserialisation problem and you should report it to https://github.com/microsoft/lsprotocol
Mhm, I can not reproduce with pipx
installed version:
package jedi-language-server 0.40.0, installed using Python 3.11.3
- jedi-language-server
Closing as known workaround and unclear cause.
I dont mind having no hints, but errors are very unpleasant:![lsperror](https://github.com/pappasam/jedi-language-server/assets/13089667/45bae65a-d400-40bc-b4a3-2da39871d1c8)
Logs and instructions are also here https://github.com/hrsh7th/cmp-nvim-lsp-signature-help/issues/36.
Log
Let me know, what further logs or instructions you need to reproduce the problem.