| Comment: | fix(sync): key the horizon cursor by the HTTP transport's URL
The cursor slice keeps a client's horizon cursor per origin, named by the internal SyncOpts.Origin, but the public Repo.Sync never set it, so a library or CLI sync kept no cursor and every request announced in full. The HTTP transport now names its peer by its URL with any password removed, as last-sync-url keeps it, and Sync passes that through. Other transports name no origin and keep announcing in full, which §6.2.6 allows. The test pulls with a credential-bearing URL and finds the cursor under the password-free one, and no config row holding the password. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk | feat/horizon-cones |
| Files: | files | file ages | folders |
| SHA3-256: |
331b540f1c80b1eaea7aa133f06dadd7 |
| User & Date: | [email protected] on 2026-10-22 15:08:35.000 |
| Other Links: | branch diff | manifest | tags |
|
2026-10-22
| ||
| 15:08 | docs(changelog): the horizon cursor check-in: 303e4c28b7 user: [email protected] tags: feat/horizon-cones, trunk | |
| 15:08 |
fix(sync): key the horizon cursor by the HTTP transport's URL
The cursor slice keeps a client's horizon cursor per origin, named by the internal SyncOpts.Origin, but the public Repo.Sync never set it, so a library or CLI sync kept no cursor and every request announced in full. The HTTP transport now names its peer by its URL with any password removed, as last-sync-url keeps it, and Sync passes that through. Other transports name no origin and keep announcing in full, which §6.2.6 allows. The test pulls with a credential-bearing URL and finds the cursor under the password-free one, and no config row holding the password. check-in: 331b540f1c user: [email protected] tags: feat/horizon-cones, trunk | |
| 15:06 | test(conformance): probe zit for horizon support in the cursor interop check-in: 8135205010 user: [email protected] tags: feat/horizon-cones, trunk | |