Repository navigation
feat: roll back from sqt dev, and run every UI demo action on its engine - #413
Merged
Merged
Conversation
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
enabled auto-merge (squash)
November 14, 2026 11:03
Deploying sqltide with
|
| 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 |
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.
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
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}/rollbackand a Roll back button on superseded deployments, gated like Promote.ui/scripts/prepare-demo.mjsruns 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.sqt devreaders. Disk, inodes and memory are hidden. Unknown selectors and unprepared steps say so and point tosqt playground. Start over resets the engine.sqt dev, and runs every prepared action on chdb-wasm.Verification
sqt devover 280 comparisons in 7 story steps.--checkpasses against the committed data.