Skip to content

fix(ui): start the UI demo over on a new engine - #415

Merged
kvlonge merged 3 commits into
mainfrom
fix/demo-start-over
Nov 14, 2026
Merged

kvlonge merged 3 commits into
mainfrom
fix/demo-start-over

Conversation

@kvlonge

@kvlonge kvlonge commented Nov 14, 2026 •

Copy link
Copy Markdown
Contributor

Why

On the live UI demo, Start over failed in Chrome and Firefox: DROP DATABASE makes ClickHouse drop tables on threads the browser engine's worker doesn't have ("Cannot schedule a task"). The story stayed off its prepared steps, so Plan refused every selection and orders stayed paused. In Firefox the error was cleared by the panel's next read, so nothing explained it. "From a time" is disabled here (no landing times), and its message didn't help. The concepts docs implied only the boundary row can be delivered twice. The sidebar showed the version that prepared the demo (0.69.1), not the release.

Changes

  • Start over replaces the engine with a new worker from the cached download, which also frees the memory dropped tables kept. If the new engine can't start, queries fail at once instead of waiting forever.
  • The live panel pauses its reads during Start over and keeps a start-over error visible.
  • Docs: replay lineage and models now say rows arriving while a build runs can be delivered twice, and a plain MergeTree target keeps those duplicates unless the model SQL or engine handles them. No behaviour change.
  • Each release PR writes its version into the demo's preparedWith and recorded /api/status; CI's --check already ignores that field.
  • In the demo, the replay window says why there's no start time to pick, and points to a pasted --start-time command and sqt playground --template streaming.

Verification

  • Firefox 159: Start over then Plan reproduced the refusal on sqltide.io; on this build every page, all 14 selections (Start over between each), Promote, Roll back and the recording fallback pass with no console errors.
  • Website demo tests in Chrome, now including Start over: 10 of 10.
  • make check-ci ui-verify passes.
  • release-please release-pr --dry-run on this branch: the 0.70.1 PR updates both demo files.
  • Website build and link check pass (131 pages, 0 broken links); both doc sections checked rendered.

Start over dropped the demo's database, and in the browser ClickHouse drops
its tables on threads the engine's worker does not have, so it failed with
"Cannot schedule a task" and left the story off its prepared steps: Plan
refused every selection and new orders stayed paused. Start over now replaces
the engine with a new worker from the download the browser has cached, which
also frees the memory dropped tables kept. If the new engine cannot start,
queries fail at once instead of waiting on the stopped one. The panel pauses
its reads while it starts over and keeps a failed start-over's error instead
of clearing it on the next read.

The demo's orders table records no landing times, so the Plan page has no
retained window for From a time. The demo now says so, and points to a pasted
command with --start-time and to sqt playground --template streaming.
@kvlonge
kvlonge enabled auto-merge (squash) November 14, 2026 16:13
@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: bd14362
Status: ✅  Deploy successful!
Preview URL: https://eaa8c937.sqltide.pages.dev
Branch Preview URL: https://fix-demo-start-over.sqltide.pages.dev

View logs

A build starts the live materialized view before it captures the inclusive
replay boundary, so every row that arrives in between can reach the target
through both, not only the row at the boundary. The replay lineage and models
pages now say so, and that a plain MergeTree target keeps those duplicates
unless the model SQL or the engine handles them.
@kvlonge
kvlonge disabled auto-merge November 14, 2026 16:32
@kvlonge
kvlonge enabled auto-merge (squash) November 14, 2026 16:32
The demo's sidebar showed the sqt version that prepared it, so it fell
behind with every release. CI already checks that prepared.json matches
the current sqt apart from that version, so each release PR now writes
its version into preparedWith and the recorded /api/status.
@kvlonge
kvlonge merged commit 9fa4098 into main Nov 14, 2026
13 checks passed
@kvlonge
kvlonge deleted the fix/demo-start-over branch November 14, 2026 17:05
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