Artifact bcb031479b3fa452325b686409dce8901759da6f7c800a38471b1600e259d8cd:
- File
internal/verify/rebuild_fossil_test.go
-
2026-10-18 21:49:37
— part of check-in
[087e1c7ce3]
on branch feat/submanifest-reader
— fix(manifest): derive the event rows fossil derives for tags and attachments
A control artifact's 'g' event comment now matches fossil byte for byte: each target introduced by an Edit link, changes sorted by target hash and full tag name, sym- tags named as tags, a branch move linked to its timeline with its own sym- changes left out, values HTML-escaped, no leading space. tag.InsertControlEvent owns the row, and AddTag writes it, as fossil's tag add does; it was missing until a rebuild or clone.
Attachment comments link the attached artifact and the ticket or tech note as fossil 2.28 does, and a deleted attachment's src is NULL. A check-in without a C card gets a NULL event comment. Hash prefixes follow hash-digits up to 64 digits (was capped at 40); the printf helpers move to fsltype so tag, ticket and attachment comments share them.
Fossil-binary oracles: a fossil-made history with tags, branch moves, wiki, tickets, tech notes, forum posts and attachments rebuilt by both, and a go-written history rebuilt by fossil, must give identical event and attachment tables. (user: [email protected], size: 8339) [annotate] [blame] [check-ins using]
-
2026-10-19 02:00:57
— part of check-in
[2e1d1e6fb7]
on branch feat/submanifest-reader
— Merge branch 'fix/tag-events' into feat/submanifest-reader
# Conflicts: # CHANGELOG.md (user: [email protected], size: 8339) [annotate] [blame] [check-ins using]
-
2026-10-18 21:49:37
— part of check-in
[087e1c7ce3]
on branch feat/submanifest-reader
— fix(manifest): derive the event rows fossil derives for tags and attachments