search

microsoft / vscode-mypy

Linting support for Python using the mypy linter.
https://marketplace.visualstudio.com/items?itemName=ms-python.mypy-type-checker
MIT License
110 stars 25 forks source link

Problems disappear temporarily when file is closed and reportingScope is set to workspace #117

Open luabud opened 1 year ago

luabud commented 1 year ago

I think this might be controlled by VS Code but filing it here just in case.

When "mypy-type-checker.reportingScope" is set to "workspace" and you have multiple files with problems reported by mypy, closing the files will make them disappear from the problems window temporarily. Once you open another file, it shows back up.

https://github.com/microsoft/vscode-mypy/assets/45497113/a3323846-d698-4895-b057-469a48bb2d01

karthiknadig commented 1 year ago

Can you set this "mypy-type-checker.trace.server": "verbose"? and collect the logs?

karthiknadig commented 1 year ago

Actually, I think I know what is going on. I will address this.

bigpick commented 5 months ago

Actually, I think I know what is going on. I will address this.

Am still seeing this today (along with other general problems with the reported problems not showing up in the Problems tab), so is safe to say this wasn't ever addressed?

FWIW, seems to only be a problem when using workspace scope and daemon. Switching the mypy-type-checker.preferDaemon to false and everything seems to work as expected.

karthiknadig commented 5 months ago

The issues with Daemon are with mypy itself. The daemon is known to have cashing bugs, hopefully future version of mypy address it.