Repository navigation
fix(ui): start the UI demo over on a new engine - #415
Merged
Merged
Conversation
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
enabled auto-merge (squash)
November 14, 2026 16:13
Deploying sqltide with
|
| Latest commit: |
bd14362
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://eaa8c937.sqltide.pages.dev |
| Branch Preview URL: | https://fix-demo-start-over.sqltide.pages.dev |
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
disabled auto-merge
November 14, 2026 16:32
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.
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
On the live UI demo, Start over failed in Chrome and Firefox:
DROP DATABASEmakes 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
MergeTreetarget keeps those duplicates unless the model SQL or engine handles them. No behaviour change.preparedWithand recorded/api/status; CI's--checkalready ignores that field.--start-timecommand andsqt playground --template streaming.Verification
make check-ci ui-verifypasses.release-please release-pr --dry-runon this branch: the 0.70.1 PR updates both demo files.