Skip to content
zit Check-in [77e2541742]
Login

Check-in [77e2541742]

Overview
Comment:Merge stream-clone: cut clone peak memory 14.2 GB -> 291 MB (fossil parity) by storing received frames wire-backed instead of buffering the whole repo's reconstructed plaintext, with section 7.7 verification moved onto the log-basis reconstruction path (a stronger round-trip parity guard).
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 77e2541742960388deb0960811beea30c99e8a234b27394494dec1f28067c2bd
User & Date: dmestas on 2026-07-16 21:10:39.395
Other Links: manifest | tags
Context
2026-07-16
22:18
Merge fcard-import: read-lenient import path lets zit parse fossil's legacy trailing-space F cards (interop with pre-2009 history) while the strict parser, writer, and RFC stay pure and artifact identity is unchanged. check-in: f98cb9177c user: dmestas tags: trunk
21:38
Create new branch named "fcard-import" check-in: d3be8fe4ac user: dmestas tags: fcard-import
21:13
Create new branch named "fcard-fix" closed check-in: 65813afbe9 user: dmestas tags: fcard-fix
21:10
Merge stream-clone: cut clone peak memory 14.2 GB -> 291 MB (fossil parity) by storing received frames wire-backed instead of buffering the whole repo's reconstructed plaintext, with section 7.7 verification moved onto the log-basis reconstruction path (a stronger round-trip parity guard). check-in: 77e2541742 user: dmestas tags: trunk
21:08
Stop buffering the whole repository's reconstructed plaintext in RAM during clone: store received frames wire-backed and verify each durable frame's section 7.7 hash against its log-basis reconstruction (sync 7.2/7.4), cutting a sqlite clone's peak memory from 14.2 GB to 291 MB with a byte-identical store and a matching trunk hash. closed check-in: 9a18bdd63d user: dmestas tags: stream-clone
20:39
Merge tcard-order: fix T-card run ordering to key on the full sign-included name token (artifact-format 4.7.16), clearing 159 wrongly-rejected branch-switch check-ins that broke zit log on deep histories. check-in: b4f2ae0ceb user: dmestas tags: trunk
Changes