Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
luabud opened this issue Aug 12, 2023 · 4 comments
Labels
bug Issue identified by VS Code Team member as probable bug needs PR

Comments

@luabud
Copy link
Member

luabud commented Aug 12, 2023

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.

mypylintallfileinconsisten.mp4
@karthiknadig
Copy link
Member

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

@karthiknadig
Copy link
Member

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

@karthiknadig karthiknadig added bug Issue identified by VS Code Team member as probable bug needs PR and removed triage-needed labels Aug 14, 2023
@bigpick
Copy link

bigpick commented Mar 20, 2024

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
Copy link
Member

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug needs PR
Projects
None yet
Development

No branches or pull requests

3 participants