github-actions[bot] opened a new pull request, #75993: URL: https://github.com/apache/airflow/pull/75993
A loop's gate can explain itself -- LoopDecision carries a reason -- but the only places that showed one were a single task instance's header and the group header's final outcome. Seeing why a loop ran as long as it did meant opening each pass in turn and reading them off one at a time. Loops already report every pass in one summary, so this needs nothing new from the API. Picking a pass scopes the group's task instances to it, since reading why a pass decided as it did tends to lead to the tasks it ran. (cherry picked from commit 6e6ae1ab7d26161fa9f7530287f3681c67431740) Co-authored-by: Brent Bovenzi <[email protected]> Co-authored-by: Claude <[email protected]> -- 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]
