Rust: a payload is one MessagePack value (bytes-after-rs) #131
Loading…
Reference in a new issue
No description provided.
Delete branch "hands/bytes-after-rs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
cultlib-gaps:follow_up:bytes-after-leaves, speccultlib-gaps:cut_spec:cut-bytes-after-rs.r1, rulingtrailing-bytes-refuse: cultcache-rs refuses a record payload with bytes after its first MessagePack value, by count, naming type and key, never echoing the tail, through one ownercheck_record_payload(depth first, then one value). Single-file, redb andload_soarun it at load for every record (as C# and Python refuse at open), and so does every raw-envelope/batch put. Vectors:bytes-after-outcomes.msgpack(4 rows) walked.Moved with it, stated: depth is now refused at load too (a store holding a past-bound payload no longer loads), and a cache whose last pull was refused refuses every write and removal (
CultCacheLoadRefused, onerequire_loadedgate) until a pull succeeds. Before, a refused pull left an empty writable cache and the nextput_prepared_batchreplaced the store; this closes that for the duplicate-index and retype refusals too. Open Low: a never-pulled cache still has that hole (follow-upcache-must-pull-before-write).Semver: Unreleased/Breaking in the cultcache-rs CHANGELOG; implies a minor bump while 0.x (0.3.1 to 0.4.0), cultnet-rs 0.3.0 to 0.4.0.
Soul: verdicts
cut-bytes-after-rs.s1to.s3(s1 load forked on index; s2 refused-load batch wiped the store; s3 holds). Reports h1 to h3. Full cultcache-rs, cultnet-rs, cultmesh-rs suites pass (914 tests). Expect a rebase on #127 (slot-readonly-rs) atdecode_payloadand the changelog head.🤖 Generated with Claude Code
892765ba) into hands/bytes-after-rs e584551fa309b825d6, slot-readonly-rs) into hands/bytes-after-rs