Repository navigation
feat(ui): job lineage graph, reworked run page and lineage inspector fixes - #1389
Merged
Merged
Conversation
… run origins, drop page intro notes The lineage inspector reuses the catalog listing the page already holds, so a click reads only the node's own facts, and it keeps the previous node's details until the next arrive instead of collapsing to a loading line. A run's origin chip opens the trigger or the run it repeats, and its kind is a plain label, instead of both filtering the run list. Explanatory paragraphs at the top of People, Roles, single sign-on, Check access, Connections, Providers and Maintenance are removed.
…oup boxed around its nodes Statements on a run page name their statement kind, and run-level queries read as run.
…le its detail loads
kvlonge
enabled auto-merge (squash)
November 9, 2026 07:43
The first failed node's error shows without a click. Timeline rows run in start order and the timeline is only as tall as its rows. Events and printed output are one filterable log, with failures tinted and query rows linking to their SQL. The header shows the start time, the project version and the command. A group run gathers its job runs' log and statements, and lists each node once.
kvlonge
changed the title
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.
Why
Audited UI work for job and run pages: one full Verify run, with each part as its own changelog entry.
Changes
UI only: no control API change.
Verification
make check-cipassed; no check-ci target readsui/.DuckShop: no project shape, data value or lifecycle is involved.
BEGIN_COMMIT_OVERRIDE
fix(ui): lineage inspector switches nodes without a loading flash, and its header always names the selected node
feat(ui): job pages draw their nodes as a lineage graph; a group draws each member job as a box around its nodes, with its last run
fix(ui): a run's origin chip links to its schedule or sensor, or to the run it reruns
fix(ui): run statements name their statement kind, and run-level queries read as "run"
chore(ui): drop intro notes from admin and platform pages
feat(ui): run page shows the first failed node's error inline, orders the timeline by start, and merges events and output into one filterable log. Opening a run with a failed node now records one error.read audit row for people with view.evidence
feat(ui): run header shows the start time, project version and sqb command; a group run's log and statements gather its job runs'
fix(ui): group runs list each node once, and a job run's statement SQL loads from its own run
fix(ui): top bar popovers such as Run now stay above page graphs
END_COMMIT_OVERRIDE