Skip to content

feat(ui): show why runs fail and which nodes are stale - #1440

Merged
kvlonge merged 2 commits into
mainfrom
feat/ui-runs-fixes
Nov 13, 2026
Merged

kvlonge merged 2 commits into
mainfrom
feat/ui-runs-fixes

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Why

The Runs and Catalog pages left a first user guessing. A run that failed before building anything showed only the worker's exit note, and the run page did not say which version of the project it ran. On a live server the catalog, lineage and Overview showed no last outcome and no staleness, because the catalog read did not report them.

Changes

  • Runs: a run that failed as a whole leads its banner with the first recorded error, with how the run ended beside it. Recorded errors stay pinned and red in the log. The run read now reports the snapshot it ran (generation, commit, uncommitted changes, sqb version, image), shown in the header and Details.
  • Catalog read: each node gains last_outcome (newest success, warn or failed attempt in the target's 25 newest runs and 25 newest failed runs within its last 500, or a newer build outside the scheduler) and definition_changed. Derived at read time; nothing stored. One bounded statement that reads only this target's runs.
  • UI: catalog, lineage and node pages show last outcome, changed and behind (a built table whose upstream data, seen through views, is newer). Overview counts stale nodes and its Rebuild opens the review page.
  • The log toolbar wraps on narrow screens.

DuckShop edge cases: not applicable; this adds reads and display, not a project shape or lifecycle sequence.

Verification

  • cargo test -p sqlbuild-orchestration catalog reads test on SQLite (PostgreSQL runs in CI): outcome from a newer build, a failed attempt before and after the build, a failure kept after 25 newer runs, the statement-count bound.
  • UI: svelte-check clean, vitest 210 passed (stale derivation through views, overview counts, failed-run banner).
  • uv sync --all-extras && make check-ci passed on this head; fensu dupes reports no new clusters.
  • Checked in a browser against a local DuckDB DuckShop server: Overview stale card and Rebuild, catalog stale filter, node pages for a changed and a behind model, run pages.

A run that fails before building any node now leads its banner with the
first error it recorded, such as a refused plan, with how the run ended
beside it. Recorded errors stay pinned and red in the log.

The run read reports the version a run executes from its snapshot:
generation, commit, uncommitted changes, the publishing sqb version and
the pinned image. The run header links the version and Details shows it,
with a long selection folded behind its node count.

The log toolbar wraps instead of overflowing on narrower screens.
The catalog listing now reports the newest decisive build attempt of each
node, from scheduler runs or a newer build outside them, and whether its
definition changed since the last recorded build. The UI derives which
built tables have older data than the nodes upstream of them, so the
catalog, lineage and Overview show changed and behind nodes, and the
Overview offers to rebuild them through the review page.
@kvlonge
kvlonge enabled auto-merge November 13, 2026 07:43
@kvlonge kvlonge added the full-verify Run the full Verify matrix on this pull request label Nov 13, 2026 — with Amp for GitHub
@kvlonge
kvlonge added this pull request to the merge queue Nov 13, 2026
Merged via the queue into main with commit 6730e20 Nov 13, 2026
73 checks passed
@kvlonge
kvlonge deleted the feat/ui-runs-fixes branch November 13, 2026 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

full-verify Run the full Verify matrix on this pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant