Caching: Update reads version and copy from one durable store read (update-copy-from-stored-bytes) #170

Merged
libby merged 6 commits from golden-write/update-from-stored-bytes into main 2026-11-13 19:55:56 +00:00

2026-11-13

Libby
ci: rerun after the runner cap cancelled run 895 at 30:02
All checks were successful
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Successful in 23m2s
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-13 19:28:58 +00:00
Libby
Caching: CandidateHomes and Home each carry their own comment (variants:finding:cut-update-from-stored-bytes.s2.candidatehomes-comment-misplaced)
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Has been cancelled
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-13 18:35:54 +00:00
Libby
ci: rerun the portability job (runs 887 and 847 ended failed and cancelled with no log)
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Has been cancelled
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-13 18:35:45 +00:00
Libby
Caching: Update reads every candidate home of T for its version and copy, refuses a two-store key and a cross-home move; pin the unpinned rules
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Has been cancelled
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-13 17:10:13 +00:00
Libby
Caching tests: pin the variant refusal message and ReadDurable leaving the store view alone; start TwoWriters rounds together
Some checks failed
CultMesh portability and performance / ubuntu-latest reactive semantics and leases (pull_request) Failing after 20m27s
The directory race test no longer collided once each attempt reads fresh, so each round
now starts both writers at a barrier.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-13 16:06:57 +00:00
Libby
Caching: Update reads its version and copy from one durable read of the home store
Add CacheBackingStore.ReadDurable (single-file and directory stores), factor the
directory pull's lease/retry load into LoadManifestPages, and make a store-backed
Update take apply's argument and the Expected version from that read, with the load's
deterministic element ids. The per-loss pull moves to the LostRace branch; a
store-less cache keeps the held copy and its codec refusal.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-11-13 16:00:55 +00:00