dstandish commented on issue #29332: URL: https://github.com/apache/airflow/issues/29332#issuecomment-2103011886
looks like what we need to do is find all the tasks “in the scope” of the teardown _(and that is, those tasks that are in between the teardown and its setup(s))_ and then just make sure they are not running. one idea for fixing:  but, it would probably be more efficient if we did not hit that block unless the direct upstreams already passed so another option would be to instead add something like this to the end  then it would only evaluate the indirect in-scope tasks are done if everything else passed. ideally perhaps, we would also be able to know that this run was the result of a clear and then don’t bother to run this check generally speaking! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
