Python-language-server: Intellisense stops working after idle

Created on 10 Feb 2020  Â·  5Comments  Â·  Source: microsoft/python-language-server

Environment data

  • Language Server version: 0.5.30.0
  • OS and version: macOS 10.15.1 (19B88)
  • Python version (& distribution if applicable, e.g. Anaconda): Python 3.6.55

Expected behaviour

Should be able to show function recommendations

Actual behaviour

Screen Shot 2020-01-31 at 8 19 02 PM

I have to restart my VSCode in order for it to work, which is really an annoying thing to do.

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

  1. Leave no activity on VSCode for at least 5-10 minutes
  2. Try to write anything

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)


Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)


Most helpful comment

I am having a similar issue on macOS 10.14, Python 3.7, MPLS version 0.5.31.0. The Language Server seems to stop working randomly when I come back to a file I was editing a few minutes ago. When it does, there is no import auto-completion/Intellisense/type info on hover/etc.

This is a major issue for me : it has been the main reason I cannot definitively switch from Jedi to MPLS. Are there any updates/ideas on what the problem is ?

Last logs in the Output panel (as you can see, the last logs date from several minutes before the current time) :
Screen Shot 2020-03-23 at 12 00 45 PM

No logs about MLPS in the Developer Tools' console.

All 5 comments

I am having a similar issue on macOS 10.14, Python 3.7, MPLS version 0.5.31.0. The Language Server seems to stop working randomly when I come back to a file I was editing a few minutes ago. When it does, there is no import auto-completion/Intellisense/type info on hover/etc.

This is a major issue for me : it has been the main reason I cannot definitively switch from Jedi to MPLS. Are there any updates/ideas on what the problem is ?

Last logs in the Output panel (as you can see, the last logs date from several minutes before the current time) :
Screen Shot 2020-03-23 at 12 00 45 PM

No logs about MLPS in the Developer Tools' console.

Can you please set "python.analysis.logLevel": "Trace" to capture more output. Thanks

@MikhailArkhipov after further experiments, it seems that MLPS "crashing" actually happens to me when switching between workspaces in a Multi-Root Workspace environment. I opened #1962 regarding the issue, as it is probably actually different from this one.

I'm still having this issue, I literally need to reload my VSCode every time for it to work again, and now its getting worst, it doesn't even last 5 minutes before it stops working again.

Would it be possible to have a notification, when this the language-server stops working?
[edit:] Because by the time i discover there is something wrong with the intellisense, the "Trace" logs are huge, and it is difficult to locate the problem.

Was this page helpful?
0 / 5 - 0 ratings