Clarify status in dmypy status output
#18331
Open
+2
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update the status message to clarify that the daemon may be busy and not necessarily stuck. The new message provides better guidance to users without prematurely suggesting killing the daemon. Fixes python#18008
|
According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Revised the status message output from the
dmypy statuscommand to eliminate potential misunderstandings about the daemon's operational state.Given the daemon’s synchronous design, the server may appear unresponsive during periods of heavy processing. When encountering a timeout, the status message could suggest that the daemon was "stuck", prompting users to prematurely consider stopping it.
Fixes #18008