-
Notifications
You must be signed in to change notification settings - Fork 194
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
Error on triggering completions in import context #121
Comments
Created davidhalter/jedi#1822 Are you sure catching is a good idea? Then the completions would not work without indication what went wrong. Or... I guess you meant reporting this as an LSP error which is fine but I feel like printing the stack trace would also be good. |
You're very diligent, thanks! Sorry for the hassle but this turned out to be an error in our side (we were incorrectly formatting a log message). Could you mention that on that Jedi issue and close it? Thanks again!
Yes, it is. We're trying to resolve labels for completion objects, but some (like modules) don't have one. That's why we need to pass when an error like that is raised. |
@ccordoba12 And why is this not a Jedi bug? I kind of disagree that you should ever catch an error :) Maybe you should catch |
Sorry, I thought it wasn't because we're trying to get signatures of completion objects here: python-lsp-server/pylsp/plugins/_resolvers.py Lines 79 to 85 in 0a2b82d
and I assumed that's not something Jedi can provide of modules. However, as you can see, we're catching any exception while doing that. So the cause of this bug was us not formatting the log message correctly.
Of course we can do that, but the reality is we don't have the man power to handle too many bug reports related to Jedi. The thing is few people know this project is a thin interface over Jedi's functionality, so they come here to report errors that have nothing to do with it. |
I can understand that :). All I'm saying is that this is wrong: |
Oh yeah, that was half the truth, sorry for that.
Ok, will do. Actually, we have very few broad exceptions like this, so I think Jedi is working really well. By the way, thanks a lot for your hard work on it, it's really awesome! |
c
.Results in a error on triggering
textDocument/completions
:It works with
import p
for example so it's something about specific completion items causing it to crash.I'm using it through LSP-pylsp in ST.
It uses default settings more or less but you can check all settings here https://github.com/sublimelsp/LSP-pylsp/blob/6cc56fa6f1b60649f2f59bffb9fe1f9beafc738f/LSP-pylsp.sublime-settings.
The text was updated successfully, but these errors were encountered: