The GitHub Actions job "Refresh image registry cache" on airflow.git/v3-3-test has succeeded. Run started by GitHub user bbovenzi (triggered by bbovenzi).
Head commit for run: 15b6495a9dd74de6012303c7e8b5f3d25b46ca0b / Pierre Jeambrun <[email protected]> Mark only a run's most recent asset event as triggering it (#71441) (#71547) * Mark only a run's most recent asset event as triggering it An asset event is linked to every dag run that consumed it, so a run that consumed several events showed "Triggered Dag Run" on each of them — in both the Asset Events view and a dag run's upstream asset events view — making it look as though more runs had been created than actually were. Only a run's most recent consumed event triggers it; the earlier ones are merely included in the run. Surfacing that distinction makes the attribution match what actually happened. closes: #56749 * Match asset event triggering by id and add an N+1 query-count test Address review feedback: match each created-dagrun reference to its source event by id instead of relying on the positional order of two parallel lists. The same asset event can trigger one dag run while being merely included in another (an asset can fan out to several consumers), so the flag is resolved per (event, run) pair. The endpoints always populate it, so it is a required field with no default. Also add a query-count assertion so both asset-event endpoints are guarded against an N+1 as the number of consumed events grows. * Small adjustments (cherry picked from commit 3f66d0f2da5c81e010ea280b24f47175cfef02f4) # Conflicts: # airflow-core/src/airflow/api_fastapi/common/db/assets.py # airflow-core/src/airflow/ui/src/components/Assets/TriggeredRuns.tsx Report URL: https://github.com/apache/airflow/actions/runs/31713175642 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
