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
{{ message }}
Repository navigation
dmypy + torch: second run produces different results (Final name must be initialized with a value) #17652
Today I tried using dmypy for the first time and noticed a really strange bug: the second run produced different results than the first run!
More specifically (and even stranger) the error message "Final name must be initialized with a value" spreads from a known false positive (#5608) to other cases.
Subsequent spread the error from cases where it is expected to cases where it is not.
$ dmypy startDaemon started
$ dmypy check srcsrc/dmypy_final_bug/__init__.py:10: error: Final name must be initialized with a value [misc]src/dmypy_final_bug/__init__.py:11: error: Final name must be initialized with a value [misc]Found 2 errors in 1 file (checked 1 source file)
$ dmypy check srcsrc/dmypy_final_bug/__init__.py:10: error: Final name must be initialized with a value [misc]src/dmypy_final_bug/__init__.py:11: error: Final name must be initialized with a value [misc]src/dmypy_final_bug/__init__.py:15: error: Final name must be initialized with a value [misc]src/dmypy_final_bug/__init__.py:16: error: Final name must be initialized with a value [misc]Found 4 errors in 1 file (checked 1 source file)
Activity
Traverse module ancestors when traversing reachable graph nodes durin…