Artifact 0465f3158068611b96788e51c35ffb8f054035ef0a694a667eab4682c446d314:
- File
horizon_test.go
-
2026-10-23 02:20:22
— part of check-in
[fe06d02a12]
on branch feat/horizon-cones
— feat(sync): name a history URL in horizon-served
draft-fossil-horizon-00 §6.2.5 lets an origin append to pragma horizon-served the URL of an interface outside the protocol at which history below a horizon can be queried, and §5.5 has a client direct the user there. go-libfossil emitted the level alone and dropped any URL a reply carried.
An origin now appends its horizon-history-url setting when set. The value rides the pragma as one raw card token, so SetConfig refuses anything but a single http or https URL with a host and no white space or credentials, and the handler emits nothing for a value stored past that check. The client records a valid URL from any origin in its clone and sync results, exported additively on the public results, and the CLI's clone and cone store/deepen print it. (user: [email protected], size: 21435) [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: 21435) [annotate] [blame] [check-ins using]
-
2026-10-23 02:20:22
— part of check-in
[fe06d02a12]
on branch feat/horizon-cones
— feat(sync): name a history URL in horizon-served