pylint errors stay around after deleting code file

[bersbersbers]

Environment data

• VS Code version: 1.21.1
• Extension version: 2018.2.1
• OS and version: Microsoft Windows [Version 10.0.16299.309]
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.6.4
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): dont know
• Relevant/affected Python packages and their versions: pylint--version
  pylint 1.8.3,
  astroid 1.6.2
  Python 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:54:40) [MSC v.1900 64 bit (AMD64)]

Actual behavior

After deleting bug.py, pylint errors for bug.py stay around.

Expected behavior

After deleting bug.py, pylint errors for bug.py are discarded. (This works for .cpp files, for example.)

Steps to reproduce:

1. Create bug.py
2. Write anything that raises a pylint error ("bug.py" is good, yields "E0602: Undefined variable 'bug'")
3. Delete bug.py

Logs

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

nothing

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

Upon deleting bug.py:

mainThreadExtensionService.ts:44 TypeError: Cannot read property 'document' of undefined
	at disposables.push.documentManager.onDidChangeActiveTextEditor (C:\Users\Username\.vscode\extensions\ms-python.python-2018.2.1\out\client\interpreter\interpreterService.js:54:91)
	at e.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:88:992)
	at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:665:650
	at e.fire (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:88:992)
	at e.$acceptDocumentsAndEditorsDelta (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:663:757)
	at e._doInvokeHandler (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:587:832)
	at e._invokeHandler (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:587:550)
	at e._receiveRequest (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:586:658)
	at e._receiveOneMessage (c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:586:427)
	at c:\Program Files\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:585:494
e.$onExtensionRuntimeError @ mainThreadExtensionService.ts:44
e._doInvokeHandler @ rpcProtocol.ts:174
e._invokeHandler @ rpcProtocol.ts:159
e._receiveRequest @ rpcProtocol.ts:108
e._receiveOneMessage @ rpcProtocol.ts:90
(anonymous) @ rpcProtocol.ts:33
(anonymous) @ rpcProtocol.ts:213
e.fire @ event.ts:142
(anonymous) @ ipc.net.ts:81
emitOne @ events.js:96
emit @ events.js:191
readableAddChunk @ _stream_readable.js:178
Readable.push @ _stream_readable.js:136
onread @ net.js:560

[brettcannon]

Can I ask why you would want linting results for a file that you deleted? I'm not seeing the use-case.

[bersbersbers]

Oh my, I have mixed up actual and expected behavior. Sorry for that! The bug is that the messages do stay around, and I would expect them to disappear.

[brettcannon]

I can't reproduce, so this seems to have been fixed.

[bersbersbers]

@brettcannon if you say you cannot reproduce: are you using some internal build that I might not have? Because I can still repro this in 1.22.2 (and 1.23.0). I should add that I usually use folder mode, so maybe this is one requirement to reproduce this.

[DonJayamanne]

@bersbersbers Please confirm you have the latest version of the extension 2018.4.0.
Please test and let us know whether you are still getting this error and feel free to re-open the issue. If yes, please do provide the logs, thanks.

[bersbersbers]

Yes, I am using ms-python.python 2018.4.0. I am still getting this error, but I agree it's harder to repro than I thought.

For example, this is how it does NOT reproduce:

• Open new instance of VS Code
• File, Open Folder, select an empty folder
• File, New File, write garbage
• File, Save As, Bug.py
• Note pylint error
• Explorer pane, right-click Bug.py, Delete
• (Pylint error disappears.)

During testing, I have noticed that the same happens with a .tex file, so I assume this is a general VS Code bug. I will report it in their repo.