Block a user
A lead can neither read nor safely keep its own held peer messages — the only drain is an injectable pane
Correction from the lead who filed this: the cause paragraph is wrong, and the ticket is more important than it says
The original body blames unreadability on a delivery failure:
So the…
The startup coverage line reports "off" for errorPattern, but legacy classification is still running
fleetd #415: split coverage() feature-state wording by pattern fallback semantics
e60f892efd
Merge pull request 'fleetd #415: split coverage() feature-state wording by pattern fallback semantics' (#423) from worker/415-coverage-wording-2cbf9c-5 into main
A lead can neither read nor safely keep its own held peer messages — the only drain is an injectable pane
Checked the two claims I made above, so whoever takes this does not have to.
The body really is available at the seam. Confirmed:
// LeadChannel.java
List<LeadMessage> peek(); …
Sweep for the REVERSE config mismatch: a boot snapshot read where the key is hot
Filed the structural gap as #427 — I said above I wanted to think about what such a checker could actually assert first, so here is the answer.
The concrete thing I did not see when I wrote…
A config key's hot/deferred class is a claim about every consumer, and nothing checks it that way
FleetHealthMonitor.coverage has no test at all, and it feeds fleet_list's healthCoverage field
Sweep for the REVERSE config mismatch: a boot snapshot read where the key is hot
Sweep for the REVERSE config mismatch: a boot snapshot read where the key is hot
Sweep done. The reverse defect exists, twice. Both filed:
- #424 —
MemberRegistryfreezesfleet.architects, so revoking an architect slot does not revoke it. This is the dangerous…
fleet_profiles reports a frozen "default" profile while placement already moved to a new one
Revoking an architect slot does not revoke it: MemberRegistry freezes fleet.architects, and the reload says it applied
Model gating units 2+3: enforce the allow-list at spawn, and turn one model off at runtime without editing profiles
A lead can neither read nor safely keep its own held peer messages — the only drain is an injectable pane
Second instance of the #399 shape: a test uses Phase.ASKING as a barrier for push-loop state published later
fleetd #418: barrier the throw-path push-loop test on state decide() reads
2d09c8b027
Merge pull request 'fleetd #418: barrier the throw-path push-loop test on state decide() reads' (#419) from worker/418-588283-3 into main
ed54f0224e
Merge pull request 'fleetd #416: fleet_list must enumerate the STARTUP profile set' (#420) from worker/416-3ad1da-1 into main
fleetd #416: fleet_list must enumerate the STARTUP profile set
fleet_list advertises free capacity for a profile the spawn gate refuses — CapacitySource reads the live profile keySet