Name the pull requests that build ADR 0270 and 0271
This commit is contained in:
+1
-1
@@ -154,4 +154,4 @@ stopped or failed.
|
||||
module opens no walk.
|
||||
- [Design 47](../03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md), *The state table* and *A
|
||||
delivery group*, which take these rows once this record is accepted.
|
||||
- mesh-catalog, the branch `fix/319-316-covered-and-lifted`.
|
||||
- mesh-catalog #150, which builds it.
|
||||
|
||||
+1
@@ -115,3 +115,4 @@ Three things were missing, read from the controller's code
|
||||
the precedent of a wait for a person said as its own condition.
|
||||
- [To-be 45](../03-DESIGN/01-to-be/45-a-core-that-cannot-fail-silently.md) §3, the signals table, and §8, the
|
||||
bus as a planned step, which take this row once this record is accepted.
|
||||
- mesh-controller #173, which builds it.
|
||||
|
||||
+1
-1
@@ -51,7 +51,7 @@ The group's order put it second. Open question 4 in the report asks whether that
|
||||
## 2026-10-09 — the fix, proposed
|
||||
|
||||
[ADR 0270](../../02-DECISIONS/0270-a-held-delivery-whose-change-already-runs-or-has-nothing-to-run-ends-by-itself-and-a-hold-whose-reason-is-gone-lifts.md)
|
||||
(proposed) answers open questions 1 and 2, and the catalogue's branch `fix/319-316-covered-and-lifted` builds it:
|
||||
(proposed) answers open questions 1 and 2, and mesh-catalog #150 builds it:
|
||||
|
||||
- **Asked and not answered is a reason to wait, not to hold.** `groupTurns` leaves a member in `published` while
|
||||
its group's composed check is asked for the current heads and has no verdict.
|
||||
|
||||
+2
-2
@@ -111,8 +111,8 @@ later walk.
|
||||
## 2026-10-09 — the fix, proposed
|
||||
|
||||
[ADR 0270](../../02-DECISIONS/0270-a-held-delivery-whose-change-already-runs-or-has-nothing-to-run-ends-by-itself-and-a-hold-whose-reason-is-gone-lifts.md)
|
||||
(proposed) gives both ends this issue asks for, by observation, and the catalogue's branch
|
||||
`fix/319-316-covered-and-lifted` builds them in mesh-delivery:
|
||||
(proposed) gives both ends this issue asks for, by observation, and mesh-catalog #150 builds them in
|
||||
mesh-delivery:
|
||||
|
||||
- **A merge that moves nothing is delivered at once.** `MovesNothing()` no longer counts `Plan.New`: a module
|
||||
the controller builds and sends nowhere opens no walk, so there is nothing to wait for. A merge whose plan moves
|
||||
|
||||
@@ -62,7 +62,7 @@ person, and the person must be told.
|
||||
## 2026-10-09 — the fix, proposed
|
||||
|
||||
[ADR 0271](../../02-DECISIONS/0271-a-send-held-for-the-buss-planned-step-is-told-to-the-operator-at-once-and-a-change-that-needs-it-says-so-before-it-merges.md)
|
||||
(proposed) takes suggested fixes 1 and 3. The controller's branch `fix/336-bus-step-waiting` builds them:
|
||||
(proposed) takes suggested fixes 1 and 3. mesh-controller #173 builds them:
|
||||
|
||||
- **Row S17**, `bus.<bus module>.step-waiting`: raised on the first watchdog tick after a walk's send was refused
|
||||
for the bus's planned step, while the new bus build would still replace the bus on its machine. It is a
|
||||
|
||||
Reference in New Issue
Block a user