-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Language server does not start in macOS application (master) #14923
Comments
Now our code completion architecture uses setuptools entry points for its providers (LSP, Kite, Fallback and Snippets). So that could be causing issues in our Mac app.
I guess the server is not even started in the app because the logs are generated as expected. |
Okay, I'm not sure what to do with that... |
Okay, I've partially solved the issue. Indeed the LSP server was not being launched because the plugin was not found. This was because it was not listed in Spyder's entry-points. #14930 should resolve this. I said partially fixed since now the LSP server starts and command completion seems to be functioning properly according to the logs, but command completion does not show in the editor for results outside the active document. Images attached. I have a module located in an entry in the PYTHONPATH Manager: First, from bootstrap everything works as expected; note the LSP server log behind the Spyder window indicating the completion result list... Next from macOS application build. For a completion in the active document, the completion is visible in the Editor and server log shown behind Spyder window. However, for the module, the server log shows that the completion is working properly, but it does not show up in the Editor. Any ideas on what could be causing this? |
Are completions working for standard modules? I mean, |
Okay, hmm. I cannot reproduce the final completions issue. Everything seems to be working properly. Maybe I had something wonky in my build environment. Anyway, wiped conda and build environments, re-tested and everything seems okay. |
Just to clarify, #14930 should entirely resolve this issue. |
What steps will reproduce the problem?
The language server does not appear to start in the macOS standalone application and command completion does not work.
Also, when running debug mode there does not appear to be any lsp logs produced. Are these in a new location?
System
The text was updated successfully, but these errors were encountered: