Fix asset events test for Dag runs without start date - #71799
Merged
hussein-awala merged 1 commit intoAug 18, 2026
Merged
Conversation
The /assets/events endpoint scopes returned events to the Dags the caller may read, resolving against DagModel. The test creates an event whose source Dag is never registered, so the scoping filter excludes it and the asset_events list comes back empty, tripping an IndexError. Register the source Dag as a real deployment would.
potiuk
approved these changes
Aug 18, 2026
seanghaeli
approved these changes
Aug 18, 2026
hussein-awala
approved these changes
Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The /assets/events endpoint scopes returned events to the Dags the caller may read, resolving against DagModel. The test creates an event whose source Dag is never registered, so the scoping filter excludes it and the asset_events list comes back empty, tripping an IndexError. Register the source Dag as a real deployment would.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.