Artifact 2db31e8aac0bb591c01152792caa214718415b17ac4a1d49bbed803d5679afb3:
- File
conformance/coverage_test.go
-
2026-10-22 22:34:36
— part of check-in
[6f8176bb93]
on branch feat/horizon-cones
— test(conformance): cover the origin's classification memo
HZ-6.2-9 and HZ-6.2-10 were gaps. The new cases read, from the handler's report of what each request's classification read, that a pull over an unchanged store reads nothing, one after a commit reads what it appended, a blob after its manifest is classified alone, a parent after the child citing it forces a full read, and a cone never classified is classified without re-reading the store; and that every reply announces what a second handle with an empty memo announces. HZ-6.2-10 is partial: a horizon's first classification walks its held set's trees from the store, as zit's does.
The case list joins the horizon suite from the coverage table, leaving the horizon case files to the work in flight there. (user: [email protected], size: 7647) [annotate] [blame] [check-ins using]
-
2026-10-22 22:48:31
— part of check-in
[7dec3e4fb3]
on branch feat/horizon-cones
— Merge branch 'wip/hz-memo' into feat/horizon-cones
The origin's classification memo (draft-fossil-horizon-00 ยง6.2): the reference graph and each cone's classification kept per store prefix and extended by appended artifacts, recomputed in full only when an arrival was already cited. A pull after a one-artifact push on fossil-scm.org's repository answers in about 0.25 s instead of 2.7 to 4.5 s. (user: [email protected], size: 7647) [annotate] [blame] [check-ins using]
-
2026-10-22 22:34:36
— part of check-in
[6f8176bb93]
on branch feat/horizon-cones
— test(conformance): cover the origin's classification memo