pylint errors stay around after deleting code file in working copy

[bersbersbers]

• VSCode Version: 1.23.1
• OS Version: Win 10 1803
• Extension Version: 1.29.0
• System Language: English
• SVN Version: TortoiseSVN 1.10.0
  svn, version 1.10.0-dev (under development)
  compiled Apr 14 2018, 10:24:15 on x86-microsoft-windows

Issue

After deleting some bug.py, pylint errors for bug.py stay around. I could repro this with python and with latex files. I have reported
microsoft/vscode#49187
yet I am told this has to do with extensions. I have reported
microsoft/vscode-python#1235
but am told they cannot reproduce.

Steps to Reproduce

In Windows Explorer:

1. Create folder "Repo" somewhere
2. Using TortoiseSVN, "create repository here"
3. Create folder "Work" somewhere
4. Checkout from "Repo"

In VS Code:

1. Install Python extension
2. Using Ctrl-K-O, open "Work"
3. Ctrl-N, type "öäü", Ctrl-S, save as "bug.py"
4. Click the "(x) 1 /!\ 0" in the status bar (bottom left) to open "Problems". Note the problem (undefined variable öäü).
5. Right-click "bug.py" in "Work", Delete
6. Note the problem sticks around.

SVN Output

Using svn "svn, version 1.10.0-dev (under development)" from "C:\Program Files\TortoiseSVN\bin\svn.exe"
[xyz]$ svn info --xml
[xyz]$ svn stat --xml --no-ignore --ignore-externals
[xyz]$ svn info --xml
[xyz]$ svn log -r BASE:HEAD -q --xml
[xyz]$ svn stat --xml --no-ignore --ignore-externals
[xyz]$ svn cat bug.py
svn: warning: W200005: 'C:\Src\xyz\bug.py' is not under version control
svn: E200009: Could not cat all targets because some targets are not versioned
svn: E200009: Illegal target for the requested operation

[xyz]$ svn stat --xml --no-ignore --ignore-externals
[xyz]$ svn stat --xml --no-ignore --ignore-externals

[bersbersbers]

Would you please care to explain why you closed this? I have a reproducible bug that occurs with a combination of VS Code, Python extension and Subversion extension. I reported it to all three and everyone is closing their issues. What is the proper way to get this fixed?

[JohnstonCode]

Because you opened two bugs #261

[bersbersbers]

Oh, I did. Sorry, I should have checked for that after a short GitHub glitch yesterday. Thanks for letting me know!

[JohnstonCode]

No problem, i have updated #261 btw.