You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When activating the daemon, only the first opened file gets linted. When switching to another file nothing happens.
There are no errors from the extension itself in the output tab of this extension. I can see that the linter gets called for the file I just switched to, but no linting errors are shown in the output either.
Making changes to a file and saving it doesn't make a difference.
Apart from all of that, linting with the daemon (if it works at all) seems slower than directly invoking mypy.
That is an issue with dmypy, python/mypy#15677 . We added the mypy-type-checker.preferDaemon setting to allow users to turn of daemon mode as it seems to have too many issues currently.
When activating the daemon, only the first opened file gets linted. When switching to another file nothing happens.
There are no errors from the extension itself in the output tab of this extension. I can see that the linter gets called for the file I just switched to, but no linting errors are shown in the output either.
Making changes to a file and saving it doesn't make a difference.
Apart from all of that, linting with the daemon (if it works at all) seems slower than directly invoking mypy.
Example Workspace
vscode-mypy.zip
My System
Version: 1.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.22621
Mypy Type Checker: v2023.6.0
Python 3.10.11
The text was updated successfully, but these errors were encountered: