Repository navigation
[v3-4-test] UI: Replace stacked Dag header banners with inline status (#74516) - #75125
Merged
Merged
Conversation
…#74516) Dag, Dag-run and task-instance headers had accumulated full-width banners that stack on each other and repeat across pages. Draining and the pending review indicator each had two separate implementations, so the same concept rendered differently depending on which page you were on. The approach follows review feedback on #74131: keep the short status inline and put the detail behind the control that reports it. Each status now sits where it can be read without crowding what it qualifies -- the deactivation marker ahead of the breadcrumb, the backfill notice beside the Dag's name, the retry reason among the task instance's own facts. Reparse was previously hidden on a Dag that had failed to parse, which is the state where it is most useful. A plugin that fails to load no longer replaces the page with an error. (cherry picked from commit 7fbcfee) Co-authored-by: Brent Bovenzi <brent@astronomer.io> Co-authored-by: Claude <noreply@anthropic.com>
1 task done
bbovenzi
marked this pull request as ready for review
October 19, 2026 16:52
bbovenzi
requested review from
bbovenzi,
choo121600,
guan404ming,
pierrejeambrun,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
October 19, 2026 16:52
Contributor
Author
|
Hi maintainer, this PR was merged without a milestone set.
|
vatsrahul1001
pushed a commit
that referenced
this pull request
Oct 20, 2026
…#74516) (#75125) Dag, Dag-run and task-instance headers had accumulated full-width banners that stack on each other and repeat across pages. Draining and the pending review indicator each had two separate implementations, so the same concept rendered differently depending on which page you were on. The approach follows review feedback on #74131: keep the short status inline and put the detail behind the control that reports it. Each status now sits where it can be read without crowding what it qualifies -- the deactivation marker ahead of the breadcrumb, the backfill notice beside the Dag's name, the retry reason among the task instance's own facts. Reparse was previously hidden on a Dag that had failed to parse, which is the state where it is most useful. A plugin that fails to load no longer replaces the page with an error. (cherry picked from commit 7fbcfee) Co-authored-by: Brent Bovenzi <brent@astronomer.io> Co-authored-by: Claude <noreply@anthropic.com>
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.
Dag, Dag-run and task-instance headers had accumulated full-width banners that
stack on each other and repeat across pages. Draining and the pending review
indicator each had two separate implementations, so the same concept rendered
differently depending on which page you were on.
The approach follows review feedback on #74131: keep the short status inline
and put the detail behind the control that reports it. Each status now sits
where it can be read without crowding what it qualifies -- the deactivation
marker ahead of the breadcrumb, the backfill notice beside the Dag's name, the
retry reason among the task instance's own facts.
Reparse was previously hidden on a Dag that had failed to parse, which is the
state where it is most useful. A plugin that fails to load no longer replaces
the page with an error.
(cherry picked from commit 7fbcfee)
Co-authored-by: Brent Bovenzi brent@astronomer.io
Co-authored-by: Claude noreply@anthropic.com