Artifact bcca6fbb8308dc8f7f1ca4605bc894a90f9f051f5b152edbdcbde69367e238c3:
- File
conformance/horizon_cluster_zit_test.go
-
2026-10-23 02:13:23
— part of check-in
[5768a5342d]
on branch feat/horizon-cones
— fix(sync): withhold a cluster a horizon request names by gimme
An origin answering a horizon-scoped request already announced no cluster in its clone, pull or sync inventory and answered req-clusters with nothing, but a gimme naming a cluster still got the cluster's file card. A horizon clone that learned a cluster's name anywhere could so still be sent one, against draft-fossil-horizon-00 §4.5 and §6.2.
The handler now drops a cluster from a gimme's answer when the request carries a horizon pragma. A new conformance case records the origin's replies to a horizon clone, pull and sync across freshly minted clusters, with and without a cursor, and to every gimme and req-clusters shape, and checks no cluster name crosses; an interop test checks zit's origin the same way. (user: [email protected], size: 4322) [annotate] [blame] [check-ins using]
-
2026-10-23 03:28:00
— part of check-in
[c4b191ed05]
on branch feat/horizon-cones
— Merge branch 'wip/hz-close-sync' into feat/horizon-cones
An origin answering a horizon request never sends a cluster, even one a gimme names; an origin may name a history URL in horizon-served (horizon-history-url), which the client reports; and a merge with no peer to ask refuses whenever either side's ancestry crosses the horizon. Conflicts in the changelog and the CLI horizon tests kept both sides. (user: [email protected], size: 4322) [annotate] [blame] [check-ins using]
-
2026-10-23 02:13:23
— part of check-in
[5768a5342d]
on branch feat/horizon-cones
— fix(sync): withhold a cluster a horizon request names by gimme