Add a way to restart the Python Language Server

[Lexicality]

If the python language server crashes or gets into an unusable state, the only way to get it working again is to reload the entire editor window. This is very inconvenient.

Environment data

• VS Code version: 1.28.2
• Extension version (available under the Extensions sidebar): 2018.9.2
• OS and version: Windows 10 version 1803
• Python version (& distribution if applicable, e.g. Anaconda): N/a
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/a
• Relevant/affected Python packages and their versions: N/a

Actual behavior

The only way to restart the Python Language Server is to reload the window

Expected behavior

A menu option to restart the python language server should be present, like with Typescript

Steps to reproduce:

N/a

Logs

N/a

[jimklo]

This is a much needed feature.

[kevindavenport]

Much needed. This exists in the Jupyter version https://donjayamanne.github.io/pythonVSCodeDocs/docs/jupyter_getting-started/

[angelhdzmultimedia]

Please add this command! It's crashing a lot! And I have to reload the whole workspace window!

[SIGSTACKFAULT]

[bump]

[angelhdzmultimedia]

[bump]

[DonJayamanne]

@AngelHdz @SIGSTACKFAULT

Please could you let is know why this is required.
I.e. if you are having issues with the language server, please could you file an issue with the details.

I understand the need for such a feature (a quick fix to get the extension working, without reloading the window), however at the same time I'd like to ensure we resolve the root cause, else restarting LS is merely going to mask the underlying problem.

Also please do upvote 👍 the issue so we can track and prioritize this issue.

[angelhdzmultimedia]

@AngelHdz @SIGSTACKFAULT

Please could you let is know why this is required.
I.e. if you are having issues with the language server, please could you file an issue with the details.

I understand the need for such a feature (a quick fix to get the extension working, without reloading the window), however at the same time I'd like to ensure we resolve the root cause, else restarting LS is merely going to mask the underlying problem.

Also please do upvote 👍 the issue so we can track and prioritize this issue.

Thank you for replying!

When I submitted the issue to the VSCode repository, it was implied that if there was any issue, that I must be an extension's fault. But I did my debugging. For my specific issue (issues with code hinting/intelli-sense), I removed every extension I could and only left this one (so I could debug Python files). The issue remained.

The issue is, after a while of working, intelli-sense just stops auto completing things, and sometimes, it throws errors like "undefined property asdfetasd". It looks like the language server just stops working and remains with cached data.

So I decided to try other languages in my other workspaces, like Dart language, Javascript, Actionscript 3.0 with the Actionscript & MXML extension, etc.

And guess what? I had the same issues!!!!

So, it's either these language's language servers malfunctioning, or is an issue with VSCode's Intellisense!

This happens to me in every VSCode version I install.

For example, few days ago I was working with Javascript. And I had the Workspace Settings *.json file opened for editing the Theme's colors.

And suddenly, I started to have errors that there were undefined things or syntax errors in that file. So I reloaded the workspace without changing anything in the file, and the errors went away!

Sometimes, just by saving the files, the errors go away.

But the code hinting/auto-complete/intelli-sense only gets solved if I reload the workspace.

[DonJayamanne]

@AngelHdz Sounds like you are experiencing issues with VS Code (if you have similar issues with other languages as well).
Please could you provide a link to the original issue.

[angelhdzmultimedia]

@AngelHdz Sounds like you are experiencing issues with VS Code (if you have similar issues with other languages as well).
Please could you provide a link to the original issue.

microsoft/vscode#80289 (comment)