ece0f28c30dfa42a9ca03c8b7a755d3b3a4d87cc
PutResource replayed a prior write by request_id alone: the dedup lookup and the schema's own UNIQUE constraint were both global, while the resource API -- and every production caller -- is per kind. A request ID reused across kinds therefore either replayed the first kind's resource with the second kind's name attached to the call, or, once the lookup was fixed, failed the insert on UNIQUE(resource_history.request_id). The step-vocabulary agreement test hit exactly this shape before its fixture was fixed to per-step IDs, which is what elevated the hazard from latent to demonstrated (archie-core-fcvd). The dedup key is now (kind, request ID) in both places: resourceByRequest filters on the kind, and schema v4 rebuilds resource_history with a UNIQUE(kind, request_id) index instead of the column constraint. Existing data satisfies the new shape -- a global constraint is strictly stricter than the per-kind one -- so the rebuild copies every row and drops nothing. Detection is the auto-index the old column constraint created, so the step is a no-op on a database that already has the v4 shape and on one created fresh.
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%