The GitHub Actions job "Tests (AMD)" on airflow.git/trigger-rule-upstream-count-memo has failed. Run started by GitHub user kaxil (triggered by kaxil).
Head commit for run: 275c6edc9f9627c4da8c1c99bf1315c869942ace / Kaxil Naik <[email protected]> Keep upstream-count memo across the UP_FOR_RESCHEDULE context rebuild are_dependencies_met rebuilds the DepContext with attrs.evolve for every UP_FOR_RESCHEDULE task instance, and UP_FOR_RESCHEDULE is in SCHEDULEABLE_STATES, so those instances reach TriggerRuleDep through the evolved context. attrs.evolve only carries over fields that __init__ accepts, so the memo's init=False meant each of them got a fresh empty dict: they neither read the memo nor warmed it for anything else. Reschedule-mode sensors fanned out behind a mapped upstream are the exact shape the memo collapses, so they were the one case opting out of it. Drop init=False (keeping the dict out of the repr instead), and route both invalidation sites through a DepContext method rather than having dagrun reach in and clear a dict only TriggerRuleDep writes. Also drop a redundant list() around _revise_map_indexes_if_mapped, which returns a list since #69565, and correct the staleness comment to name both invalidation points. Report URL: https://github.com/apache/airflow/actions/runs/30446141206 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
