-
Notifications
You must be signed in to change notification settings - Fork 285
Key error with multiple open projects #290
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
Hey! Thanks for filing such a complete ticket, appreciate the work you put into putting together repro steps. Just from a quick inspection of the log from the client, it seems like the client never sends a didOpen for Out of curiosity, what do you mean when when you say the language server crashed? Does the process exit? From the trace it seems like the server is resilient to these errors and responds with a server error to the client |
Yep, I think you're right. I only see a |
do you think its fair to say that this is a client issue, and that we can close this out? |
Well, I have absolutely no idea ^^ If you are sure about it, let's just close it. |
Can be closed now. |
Hello,
I'm repeatedly facing python language server produce a `Server Error' messages when jumping to definition between multiple projects.
I think it's linked with issue #263, but for me it happens only when working with multiple python projects.
I'm not sure if this is a client or server issue, so I'm going to file an issue in both.
I'm currently using linux, neovim 0.2.2, LanguageClient-neovim tag 0.1.40, python-language-server 0.15.1
I've build some (not so) minimal steps in order to reliably reproduce the errors.
I'm using cookiecutter in order to create easily multiple projects.
Then create a class Test in test/test.py
Next, generate another project test2
Create a new class Test2 that inherit from Test in test2/test2.py
Finally, define
PYTHONPATH
variable to make the projects importable:Here's a minimal init.vim:
Here are the steps to crash the server:
test
variable: the server has crashedHere are the log file for the server:
Here is the log file for the client:
Sorry for the super long issue, but I'd figure that if I was going to report the bug, I was going to do it properly.
Thanks for the help!
The text was updated successfully, but these errors were encountered: