Repository navigation
[self-care:calesi-design-principles] Reject mismatched SQLite keyset continuation keys - #20320
Merged
mnkiefer merged 1 commit intoNov 7, 2026
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
mnkiefer
marked this pull request as ready for review
November 6, 2026 23:52
mnkiefer
deleted the
self-care/calesi-sqlite-keyset-keys-5271c1b0275db2be
branch
November 7, 2026 04:33
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.
SQLite's local reader accepted keyset continuation pages whose key names differ from the resolved page plan. PostgreSQL rejects them as stale. This patch makes SQLite reject them too, and adds a shared conformance case that covers both backends.
Action: Dashboard server maintainer should review the change and accept it if
TestReadContractpasses for both PostgreSQL and SQLite. The fix is proposed only; it is not deployed or accepted.Finding
83f12ba71108396f1b752fe01e64a5e15c4b20fb.server/internal/dashboardstore/store.go,KeysetPageandReader.server/internal/server/server.go:1780-1805builds theKeysetPage.server/internal/postgresx/sql_plan.go:58-79checks the boundary, comparator, key count and each key name.server/internal/sqlitex/query.go:50-60checked only the boundary and comparator.server.govalidates the cursor before calling the store. A directReadercaller still saw the divergence.Validation
TestReadContract/sqlite/keyset-continuation-keysfailed with "mismatched continuation keys were accepted".go test -race ./internal/dashboardstore ./internal/sqlitexpassed against an isolated local PostgreSQL 18.go vet ./...,gofmt,golangci-lint fmt --diff,golangci-lint runon the touched packages, andgit diff --checkwere clean../internal/serverhas failures that predate this change.TestWorkflowListContractUsesPostgresfails identically on the unchanged baseline with a missingrunspartition. The role-privilege tests need a numeric-loopback admin, which my Unix-socket local database did not provide. I did not run the full./...suite.golangci-lint run ./...was run only on the two touched packages, not the whole module.Control Plane
42311677914-3489githubnext/gh-caogh-aw-workflow-id: self-care-calesi-design-principles