Skip to content

zero-swift: client and storage fixes from the bug sweep #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tmm merged 5 commits into from
Oct 22, 2026
Merged

zero-swift: client and storage fixes from the bug sweep #13

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8eb5451
test(zero-swift): sweep tests for swift-client-fixes
ampagent Oct 22, 2026
6dfb387
fix(zero-swift): a poke that changes nothing marks got queries author…
ampagent Oct 22, 2026
86a7ccb
fix(zero-swift): <= and >= filters never match NaN
ampagent Oct 22, 2026
618a0a6
fix(zero-swift): storage failures reach every client and busy writes …
ampagent Oct 22, 2026
caec772
test(zero-swift): await a task instead of a semaphore in the busy test
ampagent Oct 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/client-fixes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'zero-swift': patch
---

A first poke that changes nothing after a reconnect or relaunch completes the got queries, as in JS. `<=` and `>=` filters no longer match `NaN`. Storage: every client sharing a database hears about a write failure, and a closed client doesn't; writes queued before a failure no longer land after it; a database busy past the busy timeout is retried by the next write instead of being a storage failure; a read failure loading the client group is reported through `onStorageFailure` and moves the client to memory; and the memory fallback after a failed open is shared by name in the process, like `.memory`.
Loading
Loading