Diagnostics appear in stdlib in open file mode with Windows Store interpreter

[MinekPo1]

The problems tab is flooded by errors in libraries I have imported in my project (in this case unittest).

Is this intended behavior? If yes, how can I disable it, its really getting in my way.

[jakebailey]

These files should not have diagnostics by default, so this sounds like a bug or misconfiguration. You didn't fill out our template; can you please provide info per https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue and your configuration?

[MinekPo1]

I apologize for not giving the necessary details; I have chosen the question preset, which did not have the necessary.

Python extension version: v2021.9.1191016588
Pylance version: v2021.9.1

Python version: 3.9.7 from Microsoft store.

Logs

Settings (filtered for python and pylance)

[jakebailey]

Those are the logs from the Python extension; can you provide trace logs from the "Python Language Server" output window instead? The instructions I linked above should show how to enable and find them.

[MinekPo1]

Sorry, I way to often skim texts instead of reading them.

output.txt

[jakebailey]

Ah, you're using open file mode. We have to know which files are actually user files (to know to ignore diagnostics in certain files), but that seems to be breaking with this interpreter. Normally, we exclude the interpreter's path, but it looks like the way the Windows Store installed version of Python is laid out is confusing that logic.

You should be able to work around this by opening a folder instead of a single file, which should more clearly help us define which files are actually in the workspace and which aren't.

[MinekPo1]

I had sadly encountered this problem in a folder workspace. The original screenshot was took in one. However I was, for whatever reason, not able to trigger the problem in either a workspace or in a file, not even on the projects from which the logs and the original screenshot were taken.

[jakebailey]

I see, that does confuse things.

You're saying that you can't reproduce it anymore? We did do a release yesterday afternoon; potentially it was fixed.

[MinekPo1]

I had encountered it today, the logs were taken about the time I had uploaded them. VS code crashed (perhaps the debug messages were to much for this poor laptop) and after that I was not able to reproduce the errors. Perhaps it did update after the crash?

[jakebailey]

Your crash in the original logs looked like #1586, which should be better handled next week, but would have only caused crashes in open-file mode.

[MinekPo1]

VS code crashed after those logs were created. When the crash occurred, I had multiple vscode windows open, a mix of files and workspaces. I'm afraid this is how much I have the energy to do today, so I will do more testing tomorrow.

[MinekPo1]

I have experienced the bug again. I believe it is triggered when using tab complete on a import statement.

Screen recording

log.txt

[MinekPo1]

@jakebailey I apologize for the tagging you, but I have provided additional details.

[jakebailey]

I'm not sure what I'm seeing in the above; your original issue was about diagnostics appearing in the stdlib, but the above doesn't show that. It seems to show some other diagnostic issue in the file where the diagnostic is in the wrong place (which isn't good either, of course).

[MinekPo1]

I don't think the issue is were the library is placed, just using tab complete on it. The diagnostics were from the locally installed library (sorry for not showing it directly) I had imported. I can do it again with other libraries, if necessary, as now I know exactly hot to trigger it.

[judej]

@MinekPo1, it has been a while and I'm wondering if you are still seeing this issue?

[MinekPo1]

@judej yes. I also opened #3261 which is somewhat related.

Would you like more information?

[heejaechang]

@MinekPo1 this issue contains multiple issues making it hard to answer.

the original issue is by design. we will show errors for any file that are explicitly opened in the editor.

The problems tab is flooded by errors in libraries I have imported in my project (in this case unittest).

for second issue linked #1782 (comment)
can you open new issue if it still repro? log shows somehow it takes 4 seconds to analyze 1 line bug.py file. analyzing why it takes so long will require a bit more info from you. and probably best if you can provide us repro steps we can follow to reproduce it ourselves.

[MinekPo1]

the original issue is by design. we will show errors for any file that are explicitly opened in the editor.

I have not opened any files from unittest.

I have however opened a new issue microsoft/vscode-python#18953

I apologize that I have not added the proper info in this issue, however this was the first time I had approached such a system.