Artifact e03393774306c90acb7714ac5983bf8738132610fd1c9c8ea11deb32f3378a16:
- File
conformance/sparse_protocol_bounds_test.go
-
2026-10-21 12:47:04
— part of check-in
[6766dd6cba]
on branch feat/submanifest-reader
— fix(sync): converge when a client drops the walk's progress
A sparse walk now sends one clone-cap cookie per round naming the row the next round starts at, with a part-walked check-in's progress. A request that returns to that check-in without echoing its progress comes from a client that drops it; the round steps past the row instead of resending the same batch forever, and the next pull fetches what the walk owed by name. A gimme in a cone request is answered densely, since the requester names it (6.4). The SC-6.2-1 note records the pull inventory's whole-store read, which matches zit's. (user: [email protected], size: 15506) [annotate] [blame] [check-ins using]
- 2026-10-21 13:02:39 — part of check-in [b71f13c4ab] on branch feat/submanifest-reader — Merge branch 'feat/sparse-keepset-walk' into feat/submanifest-reader (user: [email protected], size: 15506) [annotate] [blame] [check-ins using]
-
2026-10-21 21:20:46
— part of check-in
[7244496a09]
on branch main
— Merge pull request #437 from danmestas/feat/submanifest-reader
feat: sub-manifest trees and sparse cones (draft-fossil-submanifests-00, draft-fossil-sparse-cone-00) (user: [email protected], size: 15506) [annotate] [blame] [check-ins using]
-
2026-10-21 12:47:04
— part of check-in
[6766dd6cba]
on branch feat/submanifest-reader
— fix(sync): converge when a client drops the walk's progress