The artifact hash prefix 6c115 is ambiguous and might mean any of the following:
6c1156942aef438da5b291dfcb372081d65ea094effc5ab2ca3cdb20c3c2ec79 -
- File
src/rfc_vectors/submanifest_a2_2_leaf.txt
— part of check-in
[32ef56aaf4]
at
2026-08-25 21:09:31
on branch rfc-vector-guard
— rfc vectors: keep them inert on disk
An unguarded vector parses as a real artifact, so Fossil crosslinks it into every clone -- two check-ins, a technote, twelve sub-manifest slices and a phantom pair that sync chases forever. Each vector now carries a leading # block; rfc_vectors.zig strips it at comptime so callers still see the exact RFC bytes.
Background and the cleanup that follows: see wiki page 'rfc-vector-ledger'. (user: dmestas, size: 342) [annotate] [blame] [check-ins using] [more...]
- File
src/rfc_vectors/submanifest_a2_2_leaf.txt
— part of check-in
[32ef56aaf4]
at
2026-08-25 21:09:31
on branch rfc-vector-guard
— rfc vectors: keep them inert on disk
6c115e8030ed07285adcd2eff43ddf98ff4ae32aa7d74f9ea17f5307ef81f2d5 -
- File src/sync_test.zig — part of check-in [2d300e174c] at 2026-07-11 14:23:46 on branch sync-fix — Queue held content for upload on a peer gimme per sync §3.2 and §3.1, resolving the held hash without minting a phantom and driving §3.7(b) continuation from the per-round file-send count instead of the peer-lacks proxy. (user: dmestas, size: 234777) [annotate] [blame] [check-ins using] [more...]