Block a user
fleetd#341: per-name guard so a later spawns different unprotected credential name still warns
fleetd #339: guard backend error sink
One flag guards two different memberCredentials WARNs, so a later leaking credential name is never reported
A member's normal report that quotes "API Error:" is recorded as a real backend outage
One flag guards two different memberCredentials WARNs, so a later leaking credential name is never reported
Merged to main as b32a30f (--no-ff; the branch was behind main). Follow-up commit d057d56
adds two tests — see below.
Build: Tests run: 1362, Failures: 0, Errors: 0, Skipped: 0, `BUILD…
A member's normal report that quotes "API Error:" is recorded as a real backend outage
Merged to main as d11d1d1 (--no-ff; the branch was behind main). Follow-up commit 6a81417
corrects a regression the fix introduced — read that part.
Build after both: `Tests run:…
The same text-match-drives-a-cooldown shape exists for ExhaustionSink, where the penalty is 30x longer
#338: cancel timed-out queued deliveries
A TIMED_OUT_QUEUED send leaves its message in the injector queue, and it is delivered later as a stale brief
A TIMED_OUT_QUEUED send leaves its message in the injector queue, and it is delivered later as a stale brief
Merged to main as a8cadd9. The branch was up to date with main — checked with
git merge-base --is-ancestor, not assumed.
Build after the merge, unpiped: `Tests run: 1357, Failures: 0,…
MessageService's use of Cancellation.DELIVERED is unpinned — the seam is tested, the caller is not
CompositePeerLauncher's single-daemon stop() shortcut can skip tab teardown, orphaning a worker tab
One flag guards two different memberCredentials WARNs, so a later leaking credential name is never reported
Two ways the injector can type into a member that is mid-turn — measure before fixing
A member's normal report that quotes "API Error:" is recorded as a real backend outage
A TIMED_OUT_QUEUED send leaves its message in the injector queue, and it is delivered later as a stale brief
fleetd#333: fleet.leaders is split, and split membership now proves reporting exists
fleet: is a third split key, sitting in the coverage checker's own escape hatch — and SPLIT_KEYS membership does not prove any reporting code exists