mesh-issues: say a delivered fix left in fixing, and flag a stale claim (hq issue 483)
mesh/merge-gate pass: builds mesh-issues → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
mesh/merge-gate pass: builds mesh-issues → novox; no bus step; every machine composes with the change as it did without (4 of 4 compose)
mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)
mesh/delivery superseded: a newer head of the same pull request
The operator found 13 issues in fixing whose fix was delivered hours before: their pull requests were linked, not in fixed-by, so their delivery was never measured, and nothing said an issue left there or a worker gone.
This commit is contained in:
@@ -102,6 +102,9 @@ type Issue struct {
|
||||
VerifyFor []string `json:"verify-for,omitempty"`
|
||||
// StuckOpen is the warning on the operator's channel said for a stuck fix and not yet cleared there.
|
||||
StuckOpen bool `json:"stuck-open,omitempty"`
|
||||
// NotResolvedOpen is the warning on the operator's channel that it is fixed and delivered and not resolved,
|
||||
// said and not yet cleared there (novox/hq issue 483).
|
||||
NotResolvedOpen bool `json:"not-resolved-open,omitempty"`
|
||||
// ReadyFor is the issues it depended on when it was last said ready (ADR 0279 §3), so one spell of
|
||||
// readiness is said once however many dependencies let it go at one delivery.
|
||||
ReadyFor []uint64 `json:"ready-for,omitempty"`
|
||||
|
||||
Reference in New Issue
Block a user