Artifact 480c9f9aa8d6a7022a531116f872e0cbc9ec65eb59c1bbedf47ffcd6583727d0:
- File
repo_attachment_test.go
-
2026-10-29 00:15:24
— part of check-in
[cfc0ab51e8]
on branch feat/attachments
— fix(attachments): stamp each attachment write after the latest for its name
A default-time deletion could share the addition's millisecond, leaving both rows latest: the deleted file stayed listed but could not be read. A synced attachment stamped in the future made a default-time deletion a silent no-op. Every write is now stamped strictly after the latest for its name -- now, or a millisecond after it -- and an explicit earlier or equal time is refused, for additions as for deletions.
The ambiguity error names the kinds that matched, and an external name of "." or ".." is refused up front. (user: [email protected], size: 27218) [annotate] [blame] [check-ins using]
-
2026-10-29 00:24:31
— part of check-in
[6520f5dbb0]
on branch main
— Merge pull request #523 from danmestas/feat/attachments
feat(attachments): fossil-compatible attachments API, with Quarry external stubs (user: [email protected], size: 27218) [annotate] [blame] [check-ins using]
- 2026-10-29 00:24:58 — part of check-in [e5b5f30ace] on branch main — Merge remote-tracking branch 'origin/main' into perf/memo-tree-encoding (user: [email protected], size: 27218) [annotate] [blame] [check-ins using]
-
2026-10-29 00:42:57
— part of check-in
[767f64016a]
on branch main
— Merge remote-tracking branch 'origin/main' into feat/receive-size-budget
# Conflicts: # CHANGELOG.md (user: [email protected], size: 27218) [annotate] [blame] [check-ins using]
-
2026-10-29 00:15:24
— part of check-in
[cfc0ab51e8]
on branch feat/attachments
— fix(attachments): stamp each attachment write after the latest for its name