Repository navigation
UI: Fix grid columns vanishing when a Dag version has been cleaned - #73514
Closed
Eason09053360 wants to merge 1 commit into
Closed
Eason09053360 wants to merge 1 commit into
Eason09053360 wants to merge 1 commit into
Conversation
`_get_serdag` is declared `SerializedDAG | None` and logs when it returns None, but the caller guarded it with `if TYPE_CHECKING: assert serdag`, which never executes at runtime. Once `airflow db clean` removes a version's serialized Dag row, the resulting AttributeError is raised inside the `StreamingResponse` generator -- after the 200 has been sent. The client gets a silently truncated NDJSON body and loses every run queued behind the failing one, with no status code to detect it by. The guard was a real `raise HTTPException(404)` until apache#52302 replaced it with the no-op assert. A 404 is no longer available that far into the stream, and skipping the run would hide task instances that are still in the database, so an unresolvable version now falls through to the flat-node path the endpoint already uses for tasks the current structure no longer contains. That makes the missing serialized Dag an expected, handled condition, and the grid re-streams every visible run on each auto-refresh, so its log drops from error to warning -- matching the existing sites for the same condition in models/taskinstance.py.
Eason09053360
requested review from
bugraoz93,
choo121600,
ephraimbuddy,
henry3260,
jason810496,
pierrejeambrun,
rawwar and
shubhamraj-git
as code owners
September 22, 2026 02:38
This was referenced Sep 25, 2026
This was referenced Sep 25, 2026
potiuk
added
the
closed because of open PR limit
Member
|
Hello @Eason09053360 - thank you for your contributions to Apache Airflow! The Airflow community has introduced a limit of 5 open pull requests at a time for contributors without write access to the repository. You currently have 33 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
This is not a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are. What we ask you to do is to make your first prioritization decision: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack. Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst. Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting |
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
2 participants
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.
Why
_get_serdagreturnsSerializedDAG | None, but the caller guarded it withif TYPE_CHECKING: assert serdag, which never runs. Afterairflow db cleanremoves a version's serialized Dag row, theAttributeErrorfires inside theStreamingResponsegenerator once the 200 is already sent: the client gets a silently truncated NDJSON body and loses every run queued behind the failing one. This was a realraise HTTPException(404)until #52302.What
routes/ui/grid.py: an unresolvable version now falls through to the flat-node path already used for tasks missing from the current structure. A 404 is no longer possible mid-stream, and skipping the run would hide task instances that still exist.errortowarning, matchingmodels/taskinstance.py. It still fires per affected run per auto-refresh — happy to dedupe per request if preferred.test_grid.py; both fail without the fix.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 5) following the guidelines