[v3-3-test] UI: Fix task states stuck stale when a run finishes quickly (#70319) - #70397
Merged
Conversation
…ly (#70319) The Grid/Graph TI-summaries stream re-fetches on an interval that is gated on the dag run still being active. When a run reaches a terminal state before the next tick fires — common for sub-interval runs on low-latency deployments — the interval is cleared without ever fetching the final task states, so node badges and grid cells stay frozen on whatever the last stream saw (often "no status") until a full remount. Re-stream once on the active→terminal transition so the final states always land, mirroring the self-gating behaviour of the polled run queries which never stop before observing a terminal state. (cherry picked from commit 47a0324) Co-authored-by: Andrew Chang <69671930+Andrushika@users.noreply.github.com>
1 task
shahar1
marked this pull request as ready for review
July 24, 2026 15:23
shahar1
requested review from
bbovenzi,
choo121600,
guan404ming,
pierrejeambrun,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
July 24, 2026 15:23
shahar1
approved these changes
Jul 25, 2026
Contributor
Author
|
Hi maintainer, this PR was merged without a milestone set.
|
vatsrahul1001
pushed a commit
that referenced
this pull request
Aug 5, 2026
…ly (#70319) (#70397) The Grid/Graph TI-summaries stream re-fetches on an interval that is gated on the dag run still being active. When a run reaches a terminal state before the next tick fires — common for sub-interval runs on low-latency deployments — the interval is cleared without ever fetching the final task states, so node badges and grid cells stay frozen on whatever the last stream saw (often "no status") until a full remount. Re-stream once on the active→terminal transition so the final states always land, mirroring the self-gating behaviour of the polled run queries which never stop before observing a terminal state. (cherry picked from commit 47a0324) Co-authored-by: Andrew Chang <69671930+Andrushika@users.noreply.github.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
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.
The Grid/Graph TI-summaries stream re-fetches on an interval that is
gated on the dag run still being active. When a run reaches a terminal
state before the next tick fires — common for sub-interval runs on
low-latency deployments — the interval is cleared without ever fetching
the final task states, so node badges and grid cells stay frozen on
whatever the last stream saw (often "no status") until a full remount.
Re-stream once on the active→terminal transition so the final states
always land, mirroring the self-gating behaviour of the polled run
queries which never stop before observing a terminal state.
(cherry picked from commit 47a0324)
Co-authored-by: Andrew Chang 69671930+Andrushika@users.noreply.github.com