You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 14, 2022. It is now read-only.
Extension version (available under the Extensions sidebar): ms-python.python (2018.12.1)
OS and version: win10 1803 (17134.590)
Python version (& distribution if applicable, e.g. Anaconda): python 2.7.13 32bit/win32
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): n/a
Relevant/affected Python packages and their versions: n/a
Expected behaviour
This is a tough bug to describe and document. I'm putting one example here and intend to add more examples as they come up. If anyone else has this problem that would be helpful)
Before I updated to v 2019.1 then rolled-back to 2018.12.1 (due to microsoft/vscode-python#4223) I did not see these errors; the language server worked as expected.
Actual behaviour
Here's the language server not recognizing 'continue' as a keyword. [Note: 'continue' or any other keyword is not the scope of the problem, this happens when say defining myList=[] then a few lines later doing myList.append(...]
Here's the big part of the bug, the language server is not getting all characters for the keyword/symbol that has been typed into the editor. As can be seen here: the language server thinks I've only typed 'continu' instead of 'continue'
This isn't just typing "lag" the problem will sometimes remain active indefinetly (until I perform the workarounds listed below), other times it will clear in ~3 seconds. Here's the problem stuck in the Problems panel:
I can get the errors to clear by hitting Ctrl+Enter on the line they are present. Or by restarting vscode.
Steps to reproduce:
hard to say, 90% it works as expected, randomly it fails.
Logs
The text was updated successfully, but these errors were encountered:
@sutt commented on Sat Feb 16 2019
Environment data
Expected behaviour
This is a tough bug to describe and document. I'm putting one example here and intend to add more examples as they come up. If anyone else has this problem that would be helpful)
Before I updated to v 2019.1 then rolled-back to 2018.12.1 (due to microsoft/vscode-python#4223) I did not see these errors; the language server worked as expected.
Actual behaviour
Here's the language server not recognizing 'continue' as a keyword. [Note: 'continue' or any other keyword is not the scope of the problem, this happens when say defining myList=[] then a few lines later doing myList.append(...]

Here's the big part of the bug, the language server is not getting all characters for the keyword/symbol that has been typed into the editor. As can be seen here: the language server thinks I've only typed 'continu' instead of 'continue'

This isn't just typing "lag" the problem will sometimes remain active indefinetly (until I perform the workarounds listed below), other times it will clear in ~3 seconds. Here's the problem stuck in the Problems panel:

I can get the errors to clear by hitting Ctrl+Enter on the line they are present. Or by restarting vscode.
Steps to reproduce:
Logs
The text was updated successfully, but these errors were encountered: