Skip to content

feat: roll back from sqt dev, and run every UI demo action on its engine - #413

Merged
kvlonge merged 2 commits into
mainfrom
feat/demo-every-button-real
Nov 14, 2026
Merged

kvlonge merged 2 commits into
mainfrom
feat/demo-every-button-real

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 14, 2026

Copy link
Copy Markdown
Contributor

Why

The browser demo at /demo/ runs a real ClickHouse, but only Promote ran on it. Plans, Execute and the Overview, Warehouse, Deployments and Runs pages were recordings that contradicted the engine panel (3 orders against 21, ClickHouse 25.8). Every button should do real work, or say plainly why not.

Changes

  • sqt dev: POST /api/deployments/{id}/rollback and a Roll back button on superseded deployments, gated like Promote.
  • ui/scripts/prepare-demo.mjs runs real sqt against the playground's ClickHouse and saves every plan the Plan page offers and the SQL of every Execute, Promote and Roll back in each story state. IDs, times and the version become slots the page fills in.
  • The demo runs that SQL on chdb-wasm and reads Overview, Warehouse, Catalog, Deployments, Runs and diffs from the engine through TypeScript ports of the sqt dev readers. Disk, inodes and memory are hidden. Unknown selectors and unprepared steps say so and point to sqt playground. Start over resets the engine.
  • CI: a demo job regenerates the data and fails on drift, compares the readers with sqt dev, and runs every prepared action on chdb-wasm.

Verification

  • Rollback route: permission refused, non-superseded refused, success (unit and ClickHouse integration).
  • Readers match sqt dev over 280 comparisons in 7 story steps.
  • All 78 prepared actions in 5 states run on chdb-wasm.
  • --check passes against the committed data.
  • UI unit tests, svelte-check, fensu, and the website demo tests (real engine and all fallbacks) pass.

sqt dev gains POST /api/deployments/{id}/rollback and a Roll back button on
superseded deployments, gated by deployment.promote like Promote.

The browser demo now runs on its ClickHouse engine everything sqt prepared
ahead: every plan the Plan page offers and the SQL of every Execute, Promote
and Roll back in each story state, with deployment IDs, run IDs, times and the
version filled in at run time. Overview, Warehouse, Catalog, Deployments, Runs
and diffs read the engine. CI regenerates the prepared data and fails on drift,
compares the demo's readers with sqt dev, and runs every prepared action on
chdb-wasm.
@kvlonge
kvlonge enabled auto-merge (squash) November 14, 2026 11:03
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Deploying sqltide with  Cloudflare Pages  Cloudflare Pages

Latest commit: fc238a0
Status: ✅  Deploy successful!
Preview URL: https://0880ed69.sqltide.pages.dev
Branch Preview URL: https://feat-demo-every-button-real.sqltide.pages.dev

View logs

@kvlonge
kvlonge disabled auto-merge November 14, 2026 11:08
…o audits, and keep the demo engine within its threads

The demo's Overview warehouse card no longer shows disk, inodes, server memory
or a capacity status the browser engine cannot measure, and Quality says the
playground defines no audits or tests. The engine reads synchronously on two
threads so it cannot exhaust the browser's thread pool, and the live panel
reads the view before its rows so a switch cannot pair one version with the
other's rows. The demo CI job builds the UI that sqt dev serves.
@kvlonge
kvlonge enabled auto-merge (squash) November 14, 2026 11:24
@kvlonge
kvlonge merged commit c9d62c6 into main Nov 14, 2026
18 checks passed
@kvlonge
kvlonge deleted the feat/demo-every-button-real branch November 14, 2026 11:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant