Overview
| Comment: | Add the new event-plane files the previous commit omitted |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
f48555164630bbb4f386fe42cc35d36a |
| User & Date: | dmestas on 2026-08-24 16:27:09.668 |
| Other Links: | manifest | tags |
Context
|
2026-08-24
| ||
| 16:32 |
Raise the derived events from the fold
checkin.created, branch.created and tag.* come off the artifact; branch.moved comes from the computed branch after RecomputeBranches, because only a branch's first check-in carries a sym- tag. Raising is not idempotent while folding is, so the fold asks the index which hashes are new before writing them. A rebuild raises nothing. check-in: a1b816cd96 user: dmestas tags: trunk | |
| 16:27 | Add the new event-plane files the previous commit omitted check-in: f485551646 user: dmestas tags: trunk | |
| 16:27 |
Publish the vocabulary on quarry.evt.<repo>.<noun>.<action>
RFC 0005 picked zit.evt., which the fold consumer already claims with a trailing wildcard — every vocabulary event would have been handed to the artifact parser. Own stream, own root, tests pinning both. check-in: 3bca39d8f5 user: dmestas tags: trunk | |
Changes
Added internal/api/evtplane_test.go version [bff9e949d0].
Added internal/events/raise.go version [d4b109c108].
Added internal/events/raise_test.go version [f95680c5ff].