Ask a module again at the next look when the bus did not answer, and fail the plan only after ten minutes (issue 1334)
mesh/merge-gate checking again: its repo-check failed at 12:59 UTC only on TestTheCataloguesDerivedSubjectsMeet, a catalogue fault (mesh-issues' dead subsc…
mesh/repo-check checking again: its repo-check failed at 12:59 UTC only on TestTheCataloguesDerivedSubjectsMeet, a catalogue fault (mesh-issues' dead subsc…
mesh/delivery superseded: a newer head of the same pull request

This commit is contained in:
2026-10-20 12:10:05 +00:00
parent b718d24f84
commit b76cbf708a
6 changed files with 400 additions and 6 deletions
+3
View File
@@ -340,6 +340,9 @@ type PlanModule struct {
State string `json:"state,omitempty"`
AskedAt *time.Time `json:"asked_at,omitempty"`
BuiltAt *time.Time `json:"built_at,omitempty"`
// BusWaitFrom is when the bus first did not answer an ask of this module (issue 1334): the module stays unasked and is
// asked again at the next look, until the bus has been silent for the bound, when the plan fails as for any refusal.
BusWaitFrom *time.Time `json:"bus_wait_from,omitempty"`
// SentAt is when the plan sent the machines running this module its new build, because a
// later tier is built by it (ADR 0163's gate): the reports that open the gate are the ones
// after this.