You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 39f1572
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: doc/rfc/stovepipe/fixer.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,4 +85,4 @@ The fixer adds one table and uses primary-key operations. Build-analysis history
85
85
86
86
Both queue controllers follow [`consumer.Controller`](../../../platform/consumer/controller.go): `Process(context.Context, consumer.Delivery) error`, `Name`, `TopicKey`, and `ConsumerGroup`. Service wiring resolves per-queue evaluators/executors, registers fix/fixsignal and their recovery behavior, and supplies host integrations.
87
87
88
-
The API layer defines the contracts; the persistence layer supplies MySQL support. Runtime controller wiring and provider adapters follow as separate changes. Initial dispatch can run before complete recovery reconciliation, while leaving completion awaiting verification.
88
+
The API layer defines the contracts; this persistence layer supplies MySQL support. Runtime controller wiring and provider adapters follow as separate changes. Initial dispatch can run before complete recovery reconciliation, while leaving completion awaiting verification.
Copy file name to clipboardExpand all lines: stovepipe/extension/storage/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,4 +51,4 @@ Resolution belongs to a later controller: a successful, authoritative final anal
51
51
52
52
`OpenBuildIssue.FixID` is the authoritative assignment for its opening. Updates replace last-observed build and assignment together under the opening/version guards. Analysis preserves assignments; fixer preserves observation fields. Resolution history and recovery evidence remain owned by build analysis; deleting a current row alone supplies no validating build reference.
53
53
54
-
The [repair RFC](../../../doc/rfc/stovepipe/fixer.md) defines persistence, publication, and observation ordering. Persistence implementations follow in the storage layer.
54
+
The [repair RFC](../../../doc/rfc/stovepipe/fixer.md) defines persistence, publication, and observation ordering. MySQL persists these fields through complete, version-guarded snapshots. Before deployment, add/backfill `build.first_fix_id`, `open_build_issue.fix_id`, and `queue.active_fix_ids`; fresh schemas include them.
0 commit comments