Block a user
4f28da62a3
Merge #499: redeploy-fleetd.sh gains an "unclear" supervisor state that cannot reach kill, and the detail survives the subshell (fleetd #492, #497)
599419f9e6
fleetd #492 follow-up: carry the unclear detail across detect_supervisor's subshell boundary
fleetd #492 follow-up: detect_supervisor must never read "could not tell" as "none"
awaitHerdr has two return-false paths and the caller reports both as "did not answer within 30s"
LeadRollover's settle poll has no bound of its own, so a regression shows up as a CI hang instead of a red test
Second instance, in a different class — found by accident, which is the point
While implementing #498 a worker tried to mutate Fleetd.awaitHerdr's interrupt check (if (false && ...)) to…
708f1795ad
Merge #502: awaitHerdr reports three outcomes with measured elapsed time, not one boolean (fleetd #498)
274afafde6
fleetd #498: awaitHerdr distinguishes deadline-passed from interrupted, with measured elapsed time
fleetd #498: awaitHerdr distinguishes deadline-passed from interrupted, with measured elapsed time
LeadRollover's settle poll has no bound of its own, so a regression shows up as a CI hang instead of a red test
Measured, not read — the suite hangs, and
Measured, not read — the suite hangs, and -Dsurefire.timeout does not rescue it
Re-checked on main at 8f59019 (after PR #496 merged, which touched this same loop).
The fixture,…
MessageServiceTest.anAlreadyCollectedTicketProducesNoNudge races the push loop's 300ms tick — reproduced on both hosts, under load
Item 3 done —
Item 3 done — MessageServiceTest swept. One barrier-by-hope instance, not four.
A worker swept all 20 Thread.sleep calls in `fleetd/src/test/java/dev/ltms/fleet/msg/MessageServiceTest.…
LeadRollover's failure logs print the CONFIGURED budget, not the measured wait — the exact thing that hid #489
LeadRollover's failure logs print the CONFIGURED budget, not the measured wait — the exact thing that hid #489
Done — PR #496 merged as
Done — PR #496 merged as 8f59019
Three commits: 3fb3311, c87cc25, e966cba.
Verified by me, not taken from the worker's report:
at e966cba (PR head): mvn clean install -> Tests…
Injector's readiness-grace warn prints the configured budget as if it were elapsed time — #494's defect, in the delivery loop
8f59019305
Merge #496: lead-rollover logs measured elapsed time and measured counts, never the configured budget (fleetd #494)
e966cbadf9
fleetd #494 follow-up (2nd pass): the grace-release line still had one constant, and its test could not tell the difference
c87cc25aa6
fleetd #494 follow-up: print the measured nudge count, and fix the sibling turn-settle timeout line
3fb331145a
fleetd #494: log measured elapsed time, never the configured budget, on a lead-rollover failure/success
fleetd #494: log measured elapsed time, not the configured budget, on lead-rollover failure/success
A sentinel that conflates "measured: no" with "could not measure" — three instances, three subsystems
Two more instances, both measured today, and one of them is a new sub-shape
Instance 4 — #500, and it is a cleaner example than the ones above
scripts/probe-member-credentials.sh on…
fleetd #494: log measured elapsed time, not the configured budget, on lead-rollover failure/success
Lead verification of
Lead verification of c87cc25 — build green, but the new test does not pin the new fix
Verified by me in a detached worktree at c87cc25, not taken from the worker's report.
mvn clean…
probe-member-credentials.sh uses mapfile (bash 4+) with no set -e, so on bash 3.2 it silently reports an empty field list
Correction to the filing, and the measurement that settles the family
The fleet01 lead challenged this ticket's severity. They were right that my original repro dropped the script's own set…
probe-member-credentials.sh uses mapfile (bash 4+) with no set -e, so on bash 3.2 it silently reports an empty field list
awaitHerdr has two return-false paths and the caller reports both as "did not answer within 30s"
fleetd #492: systemd --user as a third supervisor in redeploy-fleetd.sh
1.
Amending my own requirement twice. One arm was wrong, and one worry does not apply here.
1. *) die is the wrong arm for the reporting switch. Use *) echo.
I asked for *) die … on…
fleetd #492: systemd --user as a third supervisor in redeploy-fleetd.sh
Two more requirements, to apply at review. Both found by the fleet01 lead.
A worker is already on the unclear state. These two go on top, and the first one is a trap that the fix itself…