Unexpected unused type ignore fix overrides #16675
Closed
Conversation
This file contains hidden or 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
This test currently fails with this error:
AssertionError: Command 3 (dmypy check -- bar.py) did not give expected output
--- Captured stderr call ---
Expected:
bar.py:2: error: Unused "type: ignore" comment (diff)
== Return code: 1 (diff)
Actual:
(empty)
It demonstrates a bug that when an module is removed using
`FineGrainedBuildManager.update` because it is not "seen" by
`fine_grained_increment_follow_imports`, then "unused type: ignore"
warnings disappear from subsequent checks.
Ref: python#9655
This test fails with the error:
AssertionError: Command 3 (dmypy check -- bar.py) did not give expected output
--- Captured stderr call ---
Expected:
bar.py:2: error: "type: ignore" comment without error code [ignore-without-code] (diff)
== Return code: 1 (diff)
Actual:
(empty)
This test illustrates that '"type: ignore" comment without error code'
errors currently disappear in the same way that 'Unused "type: ignore"'
errors do as described in python#9655.
Ref: python#9655
This test fails with the error:
AssertionError: Command 3 (dmypy check -- bar.py) did not give expected output
--- Captured stderr call ---
Expected:
bar.py:4: error: Name "a" may be undefined [possibly-undefined] (diff)
== Return code: 1 (diff)
Actual:
(empty)
This test illustrates that possibly-undefined errors currently disappear
in the same way that 'Unused "type: ignore"' errors do as described in python#9655.
Ref: python#9655
These tests show how some errors disappear on a re-run of dmypy after a file is altered.
This which fixes issue python#9655 wherein some types of error would be lost when a file was re-processed by dmypy. Regression tests are also included. This also fixes another error where sometimes files would not be re-processed by dmypy if the only error in the file was either "unused type ignore" or "ignore without code".
This catches a regression caused by the previous commits where "type: ignore" comments are erroneously marked as unused in re-runs of dmypy. As far as I can tell, this only happens in modules which contain an import that we don't know how to type (such as a module which does not exist), and a submodule which is unused.
Before this change, fine-grained builds could spuriously mark ignored legitimate errors as "unused ignores". By keeping track of these ignored errors we ensure that enough analysis is done to know that the ignored lines are actually useful. We have to change is_errors_for_file so that we don't consider files as faulty when all of their errors were hidden.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is a demo PR to support #15043.
It demonstrates how adding
overridedecorators gets most of the newly failing tests passing (just look at the final commit).Outstanding tests