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
Python version: 3.12
Type of virtual environment used: venv, created by Poetry (version 1.8.4)
Operating system: Windows 11
Version of tool extension you are using: 2024.1.13171012
Behaviour
Expected Behavior
When the plugin option mypy-type-checker.preferDaemon is set to true and mypy-type-checker.reportingScope is set to workspace, I expect the plugin to perform type checking at a speed close or as fast to mypy-type-checker.preferDaemon is set to false.
Actual Behavior
Despite having preferDaemon and reportingScope set, the plugin runs much slower compared to running mypy directly from the command line. This significant speed difference is clearly visible in the logs, leading me to believe this might be a bug with the plugin.
Also,when preferDaemon is enable,when user save file to fix one error of it,the daemon process seems stucked.
Reproduction Steps:
Ensure the plugin option mypy-type-checker.preferDaemon is set to true.
Set mypy-type-checker.reportingScope to workspace to enable type checking across the entire workspace.
Open a large Python project and run type checking within VSCode.
I'd like to offer a reproduce repo if need.
See the logs between the different run case under preferDaemon is enable or not.
Logs:
For the readability,I have shortened some of the process logs. The full logs are included in the 'Extra Details' section.
WendaoLee
changed the title
Use daemon of mypy is slower than not used,and may get stucked when user made changes.
Use daemon of mypy is slower than not used,and may get stucked when user save changes.
Nov 18, 2024
@WendaoLee Can you provide a repro? also what is the version of mypy that you are running from the terminal? does it match the one shipped with the extension?
@WendaoLee Can you provide a repro? also what is the version of mypy that you are running from the terminal? does it match the one shipped with the extension?
does it match the one shipped with the extension?
Oh,sorry. I haven't noticed that.I have installed mypy of version 1.13.0 in my venv.Is this the reason?
Diagnostic Data
Python version: 3.12
Type of virtual environment used: venv, created by Poetry (version 1.8.4)
Operating system: Windows 11
Version of tool extension you are using: 2024.1.13171012
Behaviour
Expected Behavior
When the plugin option
mypy-type-checker.preferDaemon
is set totrue
andmypy-type-checker.reportingScope
is set toworkspace
, I expect the plugin to perform type checking at a speed close or as fast tomypy-type-checker.preferDaemon
is set tofalse
.Actual Behavior
Despite having
preferDaemon
andreportingScope
set, the plugin runs much slower compared to runningmypy
directly from the command line. This significant speed difference is clearly visible in the logs, leading me to believe this might be a bug with the plugin.Also,when
preferDaemon
is enable,when user save file to fix one error of it,the daemon process seems stucked.Reproduction Steps:
mypy-type-checker.preferDaemon
is set totrue
.mypy-type-checker.reportingScope
toworkspace
to enable type checking across the entire workspace.preferDaemon
is enable or not.Logs:
For the readability,I have shortened some of the process logs. The full logs are included in the 'Extra Details' section.
Logs when
preferDaemon
is enabled.Logs when
preferDaemon
is disabledOutcome When Attempting Debugging Steps:
Did running it from the command line work?
mypy
command directly was faster.mypy path/to/your/project
was significantly less than running it within the VSCode plugin.Extra Details
mypy.ini
:Full logs of
preferDaemon
is enabledFull logs of
preferDaemon
is disabledThe text was updated successfully, but these errors were encountered: