The artifact hash prefix 2772d is ambiguous and might mean any of the following:
2772d28b8c0ad97687aff0ae40a3d5da993e1499a6a136fc187334938856b8d5 -
- File src/sync_test.zig — part of check-in [0e5cc09150] at 2026-07-16 07:23:55 on branch container — Extract the §4.1 zlib container codec into one leaf module (src/container.zig) so logstore, repostate, and sync share a single §4.1-capacity-semantics implementation instead of three drifting copies. (user: dmestas, size: 383889) [annotate] [blame] [check-ins using] [more...]
2772dd3942e739dabffb0edca9033f8e23a1c2e973351808651558ae68d24f28 -
On tcl's tip zit ls drops from 58.3s to 0.31s: the derived state it needed was already in the cache, in the zero-parse image, and the verb asked for the record-body replay anyway.
Adjacency arrived in the image last change; what remained was every read that went around the accessors. events, its count, and store.count are all empty on an image backing, so a bound taken from them read zero and a branch value read from tagxref fell back to main_branch for every rid -- the section 8.4 walk then never left the branch and answered start:/root: with a check-in from somewhere else, exit 0 and no diagnostic. Those reads route through hasEvent, mtimeOf, hashOf, ridCount and eventsIter now, which name one enumeration order for both backings rather than inheriting insertion order from one of them.
info stays on the full derive: amend --comment stores its override as a tag, and the image carries no tag tables, so on the fast path info printed the manifest's original comment. An existing test caught that the moment the verb moved; branch and tag stay behind for the same reason. by dmestas on 2026-08-18 02:18:20.