ltms - Gitea

ltms merged pull request fleet/fleetd#596

2026-09-19 10:13:27 +02:00

#568: add hunter member role

ltms commented on issue fleet/fleetd#591

2026-09-19 10:10:59 +02:00

A lead-side rule has no delivery surface: fleet.charters reaches only spawned members, and it is per-daemon — so an operator policy aimed at "the fleets" cannot reach a single lead

CORRECTION 3, and an architect design position

An architect member (profile sol, branch worker/591-dab0a9-4) was asked to design the delivery surface. It read the code and returned a…

ltms commented on issue fleet/fleetd#568

2026-09-19 10:07:23 +02:00

The hunter skill has no MemberRole, so every sweep is spawned under a role whose agent file contradicts it

Correction to the #568 brief — read before you commit

A rule your brief did not carry. It reaches you here rather than as a message because a message cannot reach a busy member.

Never…

ltms commented on issue fleet/fleetd#589

2026-09-19 10:07:21 +02:00

Fleetd.main's wiring has 1 behavioural test across 44 sites: pin the 11 whose failure silently turns off a control, with runtime tests not source-text ones

Correction to both #589 briefs — read before you commit

This is a rule your brief did not carry, and on this ticket it is load-bearing. It reaches you here rather than as a message because a…

ltms commented on issue fleet/fleetd#591

2026-09-19 10:05:08 +02:00

A lead-side rule has no delivery surface: fleet.charters reaches only spawned members, and it is per-daemon — so an operator policy aimed at "the fleets" cannot reach a single lead

The instrument got used across two hosts today, and it found a divergence nobody knew about

Follow-up to the correction above. The fleet01 lead and I ran the charterSha256 comparison…

ltms commented on issue fleet/fleetd#591

2026-09-19 10:02:00 +02:00

A lead-side rule has no delivery surface: fleet.charters reaches only spawned members, and it is per-daemon — so an operator policy aimed at "the fleets" cannot reach a single lead

Correction — one claim in the description is wrong

The description says charters are applied by hand on each host "with nothing comparing the results". **That is false, and the fleet01 lead…

ltms opened issue fleet/fleetd#595

2026-09-19 10:00:33 +02:00

Should a lead be rolled on a timer to pick up instruction changes? Measured: the roll is the expensive answer, it contradicts a stated invariant, and it has never been observed working end-to-end

ltms opened issue fleet/fleetd#594

2026-09-19 10:00:20 +02:00

LeadRollover refuses to touch a BLOCKED lead and documents why; LeadHeartbeatLoop:161 gates on injectable() and accepts one — the same question answered both ways in one codebase

ltms pushed to main at fleet/fleetd

2026-09-19 09:57:09 +02:00

a639969a9a CLAUDE.md: a blocked lead consults architects, not the operator

ltms opened issue fleet/fleetd#593

2026-09-19 09:56:43 +02:00

redeploy-fleetd.sh knows which supervisor it is talking to (#492) but not which one it is watching: the log source and the pid count are both still macOS-shaped, and on systemd they fail in opposite directions

ltms opened issue fleet/fleetd#592

2026-09-19 09:52:29 +02:00

An architect-settled decision leaves no trace the operator can find: there is no event for it, and #392 shows there is no sink to send one to

ltms opened issue fleet/fleetd#591

2026-09-19 09:52:16 +02:00

A lead-side rule has no delivery surface: fleet.charters reaches only spawned members, and it is per-daemon — so an operator policy aimed at "the fleets" cannot reach a single lead

ltms opened issue fleet/fleetd#590

2026-09-14 08:32:30 +02:00

A broker unreachable at boot silently disables coordination for the process lifetime, and then reports itself as "not configured"

ltms pushed to main at fleet/fleetd

2026-09-13 02:14:39 +02:00

17c3a69c57 docs: CB-591 gateway page had two claims that went stale

ltms opened issue fleet/fleetd#589

2026-09-12 16:53:08 +02:00

Fleetd.main's wiring has 1 behavioural test across 44 sites: pin the 11 whose failure silently turns off a control, with runtime tests not source-text ones

ltms commented on issue fleet/fleetd#587

2026-09-12 16:52:19 +02:00

Fleetd.java: sweep every constructor-arg wiring site and report which ones no test would notice being rewired

Result: 44 sites measured, and the headline is not the one either half reported

Both halves are in. Part A swept lines 158–505 (27 sites), Part B swept 512–888 (17 sites). One mutation per…

ltms commented on issue fleet/fleetd#588

2026-09-12 16:45:40 +02:00

Every async ticket dies at a hardcoded 30 minutes, so any unit longer than that always reports failed while the member is still working — 41 measured at exactly 1800s

Closing the second "what I did not measure" bullet: nothing pins ASYNC_TIMEOUT_MS, and the coverage that looks like it does comes in through a different door.

$ grep -rn 'ASYNC_TIMEOUT_M…

ltms closed pull request fleet/fleetd#579

2026-09-12 16:42:53 +02:00

fleetd #562: surface loop health

ltms closed pull request fleet/fleetd#580

2026-09-12 16:42:45 +02:00

fleetd #571: add TIMED_OUT_UNCONFIRMED for ATTEMPTED-delivery timeouts

ltms closed pull request fleet/fleetd#584

2026-09-12 16:42:37 +02:00

fleetd #562 follow-up: extract loopHealthSource factory, pin its wiring (supersedes #579)