Rust: batch writes merge onto the store (rs-batch-merges-onto-store) #135
2026-11-12
Rust: pin push_all replacing a record held under another schema id
All checks were successful
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 20m14s
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Rust: batch merge retains by (type, key), repeated staged keys land last, dead dangling-link branch removed
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Has been cancelled
Soul findings on #135: the single-file merge matched on schema id where push matches on type, so a record under another schema id was refused as a retype; redb refused a batch repeating a key; the owned redb merge and a stale revert were unpinned; write_all_unlocked kept a dangling-link branch no caller can reach. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Rust: batch writes merge onto the store (rs-batch-merges-onto-store)
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Has been cancelled
push_all applies the given entries onto the store as it is under its lock or transaction instead of replacing it, so a cache with a stale image cannot drop a record another writer added. put_prepared_batch sends only its staged records. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>