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
Currently it fails, presumably because we don't reprocess a.py. This however points to a larger potential problem, currently we are relying on reprocessing targets with errors. However, a better idea might be to only rely on fine grained dependencies. Of course, we can cache errors and just show them if a target had errors and was not reprocessed.
The text was updated successfully, but these errors were encountered:
I've been pondering this idea some and think it is a good idea, if we can make it work. I was not able to (in the time I've spent thinking about it) come up with an example that should rely on reprocessing errored targets in any fundamental way, but I might be missing something.
From an engineering perspective, update is currently structured around clearing the errors before looking at each file and then reprocessing errored targets in order to collect all the errors, but I think it shouldn't be too hard to just clear the errors for code we reprocess
Consider this test case:
Currently it fails, presumably because we don't reprocess
a.py
. This however points to a larger potential problem, currently we are relying on reprocessing targets with errors. However, a better idea might be to only rely on fine grained dependencies. Of course, we can cache errors and just show them if a target had errors and was not reprocessed.The text was updated successfully, but these errors were encountered: