ltms - Gitea

ltms opened issue fleet/fleetd#509

2026-09-12 05:36:12 +02:00

#505 follow-up: the two-client completeness fold is unpinned, and legacyPrincipal can still re-open the escalation

ltms pushed to main at fleet/fleetd

2026-09-12 05:35:43 +02:00

40c593cd09 Merge #508: a herdr error during the pane scan is refused, not promoted to primary (fleetd #505)

36870836aa fleetd #505: a herdr error during the pane scan must not read as a clean negative

Compare 2 commits »

ltms merged pull request fleet/fleetd#508

2026-09-12 05:35:42 +02:00

fleetd #505: refuse (not promote) a caller whose pane scan errored

ltms commented on issue fleet/fleetd#505

2026-09-12 05:30:18 +02:00

A herdr error during the pane scan makes a worker's connection resolve as the primary — #317's escalation, through the door #317 did not close

Why fleetd #415's antidote does not cover this, and where the guard actually belongs

The fleet01 lead made this structural point from an older revision and flagged their premise as unverified.…

ltms commented on issue fleet/fleetd#500

2026-09-12 05:29:56 +02:00

probe-member-credentials.sh uses mapfile (bash 4+) with no set -e, so on bash 3.2 it silently reports an empty field list

It is a three-way conflation, not a two-way one — and the third cause is the one that matters

The fleet01 lead derived this from the lines I quoted and flagged it as unmeasured. I measured…

ltms opened issue fleet/fleetd#507

2026-09-12 05:27:44 +02:00

MessageServiceTest's coalescing tests sleep because the only observation available collects the ticket — the instrument is missing, not the test

ltms opened issue fleet/fleetd#506

2026-09-12 05:27:23 +02:00

Tests that stay green when the behaviour is absent: four sites, three mechanisms, one cheap discriminator

ltms commented on issue fleet/fleetd#500

2026-09-12 05:25:36 +02:00

probe-member-credentials.sh uses mapfile (bash 4+) with no set -e, so on bash 3.2 it silently reports an empty field list

The fix section above is wrong. Do not brief a worker from it.

The fleet01 lead drew a consequence I had missed, and it invalidates the fix I asked for. Measured here before accepting it.

###…

ltms commented on issue fleet/fleetd#500

2026-09-12 05:21:45 +02:00

probe-member-credentials.sh uses mapfile (bash 4+) with no set -e, so on bash 3.2 it silently reports an empty field list

Settled on real bash 3.2, and my earlier reasoning here was incomplete

The fleet01 lead challenged the severity: if set -u fires on the array expansion, the script aborts loudly rather…

ltms commented on issue fleet/fleetd#497

2026-09-12 05:15:01 +02:00

A sentinel that conflates "measured: no" with "could not measure" — three instances, three subsystems

A wider sweep for this family, recovered late

The #492-followup worker dispatched an Explore agent to look for the same shape across the repo and put the list in its reply. That reply was lost…

ltms closed issue fleet/fleetd#492

2026-09-12 05:14:39 +02:00

redeploy-fleetd.sh is launchd-only: on fleet01 it kills the daemon and leaves TWO running

ltms commented on issue fleet/fleetd#492

2026-09-12 05:14:34 +02:00

redeploy-fleetd.sh is launchd-only: on fleet01 it kills the daemon and leaves TWO running

Fixed and on main at 136312f, via PR #495 (the systemd branch) and PR #499 (the "unclear" state that closes the gap #495 left). #499 was built on #495's branch, so one merge carried both.

**Wh…

ltms closed pull request fleet/fleetd#495

2026-09-12 05:14:13 +02:00

fleetd #492: systemd --user as a third supervisor in redeploy-fleetd.sh

ltms commented on pull request fleet/fleetd#495

2026-09-12 05:14:07 +02:00

fleetd #492: systemd --user as a third supervisor in redeploy-fleetd.sh

Closing: this branch's work is already on main, merged as part of PR #499, not abandoned.

PR #499 was built on top of this branch rather than on main — its own description says "based on…

ltms opened issue fleet/fleetd#505

2026-09-12 05:13:45 +02:00

A herdr error during the pane scan makes a worker's connection resolve as the primary — #317's escalation, through the door #317 did not close

ltms closed issue fleet/fleetd#501

2026-09-12 05:11:24 +02:00

Injector's readiness-grace warn prints the configured budget as if it were elapsed time — #494's defect, in the delivery loop

ltms commented on issue fleet/fleetd#501

2026-09-12 05:11:19 +02:00

Injector's readiness-grace warn prints the configured budget as if it were elapsed time — #494's defect, in the delivery loop

Fixed and merged in PR #503, merge commit 136312f on main.

What changed. Injector now stamps System.currentTimeMillis() on the first poll where a target is not deliverable, and the…

ltms merged pull request fleet/fleetd#503

2026-09-12 05:07:36 +02:00

fleetd #501: readiness-grace expiry logs measured elapsed time and poll counter

ltms pushed to main at fleet/fleetd

2026-09-12 05:07:36 +02:00

136312fb11 Merge #503: Injector's readiness-grace warn prints measured elapsed time, never arithmetic on constants (fleetd #501)

ac351ee1de fleetd #501: readiness-grace expiry logs measured elapsed time and the loop's own poll counter, never the configured budget

Compare 2 commits »

ltms opened issue fleet/fleetd#504

2026-09-12 05:04:28 +02:00

redeploy-fleetd.sh: four places where a failed command is reported as a clean result