Python: a payload is one MessagePack value (bytes-after-py) #129
Loading…
Reference in a new issue
No description provided.
Delete branch "hands/bytes-after-py"
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-py.r1, rulingtrailing-bytes-refuse: cultcache-py refuses a record payload with bytes after its first MessagePack value, by count, naming the type, never echoing the tail; the depth refusal wins over the tail (as in C#) through one ownerread_payload_tree, which the witness bundle decode also uses. Vectors:bytes-after-outcomes.msgpack(4 rows) walked.Semver: cultcache-py manifest to 0.4.0 in this change; cultnet-py and cultmesh-py pins raised to
cultcache-py>=0.4.0; a ported dependency-range test (packages/cultnet-py/tests/test_declared_dependency_ranges.py) pins the pairing. Unreleased/Breaking entries in the changelogs.Soul: verdicts
cut-bytes-after-py.s1to.s3(s1 depth-vs-tail ordering, s2 reader-less pin; s3 holds). Open Lows: range test skips in CI (shallow checkout, no tags), shard-log replay silently skips a stamp-routed unknown schema with a tail, an inertExtraDatabranch in schema inference; follow-upstore-push-raw-tail-py. cultcache-py 231, cultnet-py 173, cultmesh-py 149 passed.🤖 Generated with Claude Code