You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(payload): actionable error from cloudsync_payload_chunks when uninitialized (#54)
Querying the cloudsync_payload_chunks vtab on a database where cloudsync
was never initialized surfaced a bare "SQL logic error": the internal
statements over cloudsync_changes failed at step time and the error code
propagated out of xFilter without ever setting the outer vtab's zErrMsg.
The /check endpoint hit this on nodes not configured for cloudsync,
while cloudsync_payload_apply already reported an actionable message.
- guard xFilter with the same is-initialized check (and message) used by
cloudsync_payload_apply
- propagate inner-statement error messages onto the vtab's zErrMsg
- stop ignoring step failures of the watermark MAX(db_version) query
- unit test: Payload Chunks Uninitialized
- e2e: Failure Path Test now asserts the forwarded "cloudsync is not
initialized" message on send, receive (non-retryable SQL error), and
sync; red against nodes still running 1.1.0, green once they run 1.1.1
- bump CLOUDSYNC_VERSION to 1.1.1 and add the CHANGELOG entry (no PG
changes, extension version stays 1.1 — no migration needed)
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,12 @@ All notable changes to this project will be documented in this file.
4
4
5
5
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).
6
6
7
+
## [1.1.1] - 2026-07-10
8
+
9
+
### Fixed
10
+
11
+
- Querying the SQLite `cloudsync_payload_chunks()` virtual table on a database where cloudsync is not initialized now raises the same actionable error as `cloudsync_payload_apply()` ("cloudsync is not initialized: call SELECT cloudsync_init('<table_name>') ...") instead of a bare "SQL logic error". Errors raised by the internal `cloudsync_changes` scan (including the watermark computation, which previously ignored them) are now propagated with their message instead of being masked.
0 commit comments