Two of the four surfaces the report named already carried it — the host has reported Held since ADR 0100, and node show reads the machine's own list. Recorded as checked rather than assumed.
Two did not, and now do. The part that carries the weight: a hold suppresses "all doing what they were told", which was true for the whole outage and acting on it is what stopped the predecessor's proxy.
Resolved by mesh-host #52 and mesh-controller #150.
Two of the four surfaces the report named already carried it — the host has reported `Held` since ADR 0100, and `node show` reads the machine's own list. Recorded as checked rather than assumed.
Two did not, and now do. The part that carries the weight: **a hold suppresses "all doing what they were told"**, which was true for the whole outage and acting on it is what stopped the predecessor's proxy.
Resolved by mesh-host #52 and mesh-controller #150.
Two of the four surfaces the report named already carried it — the host
has reported Held since ADR 0100, and node show reads the machine's own
list with an `as of` beside it. Recorded as checked rather than assumed.
Two did not. The apply line counted what it applied and said nothing
about the difference; status read the mesh's take-time listing, so a
module assigned after it showed nothing at all.
Both now say it, and the part that carries the weight: a hold suppresses
"all doing what they were told, all heard from, running what the mesh
would send them". That sentence was true for the whole outage, and acting
on it is what stopped the predecessor's proxy. Being adopted still does
not suppress it — a mode somebody chose is not a half-finished action.
Status does not call a hold a fault, deliberately. It is correct
behaviour, and a reader trained to see red for something the mesh did
right stops reading.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two of the four surfaces the report named already carried it — the host has reported
Heldsince ADR 0100, andnode showreads the machine's own list. Recorded as checked rather than assumed.Two did not, and now do. The part that carries the weight: a hold suppresses "all doing what they were told", which was true for the whole outage and acting on it is what stopped the predecessor's proxy.
Resolved by mesh-host #52 and mesh-controller #150.