ltms
0 Followers · 0 Following
  • Joined on 2026-03-08
Repositories Projects Packages Public Activity Starred Repositories
ltms opened issue fleet/fleetd#518 2026-09-12 06:07:00 +02:00
Nothing tests that FleetMcp uses the CallerResolver — forcing the legacy identity path leaves the whole suite green at 1696/0
ltms pushed to main at fleet/fleetd 2026-09-12 06:06:14 +02:00
8f02576df6 Merge #515: pin the two-client completeness fold, and legacyPrincipal earns no authority (fleetd #509)
32408d1e64 fleetd #509: pin the pane-scan completeness fold, and stop legacyPrincipal handing out primary
Compare 2 commits »
ltms merged pull request fleet/fleetd#515 2026-09-12 06:06:13 +02:00
fleetd #509: pin the pane-scan completeness fold; harden legacyPrincipal
ltms closed issue fleet/fleetd#511 2026-09-12 06:01:13 +02:00
#493 follow-up: the drain-gate abort message names a recovery that does not work, and jar_id()'s default is unpinned
ltms opened issue fleet/fleetd#517 2026-09-12 06:01:07 +02:00
A source-text test pins what a message SAYS and never whether it is REACHED — the drain-gate abort branch can be disabled with the suite green
ltms merged pull request fleet/fleetd#514 2026-09-12 06:00:24 +02:00
fleetd #511: fix wrong --no-build wording in drain-gate abort, pin jar_id() default
ltms pushed to main at fleet/fleetd 2026-09-12 06:00:24 +02:00
525bc1c5f4 Merge #514: the drain-gate abort message names a recovery that works, and jar_id()'s default is pinned (fleetd #511)
6e23bf8309 fleetd #511: fix wrong --no-build wording in drain-gate abort, pin jar_id() default
Compare 2 commits »
ltms commented on issue fleet/fleetd#507 2026-09-12 05:58:31 +02:00
MessageServiceTest's coalescing tests sleep because the only observation available collects the ticket — the instrument is missing, not the test

Second clause: mutate the instrument as well as the subsystem

Following on from my last comment. The fleet01 lead pointed out that my discriminator cannot find the defect I just described, and…

ltms commented on issue fleet/fleetd#511 2026-09-12 05:58:16 +02:00
#493 follow-up: the drain-gate abort message names a recovery that does not work, and jar_id()'s default is unpinned

Read these two in the right order: the abort message first

I filed item 1 (the wrong abort message) as the smaller of the two and item 2 (jar_id's unpinned default) as the more interesting…

ltms opened issue fleet/fleetd#513 2026-09-12 05:56:51 +02:00
MessageService's TIMED_OUT_QUEUED javadoc says the message is still queued; the code 12 lines of behaviour later cancels it
ltms closed issue fleet/fleetd#493 2026-09-12 05:53:55 +02:00
redeploy-fleetd.sh builds into the LIVE jar path, so the shutdown drain can die on a class it never loaded (#413)
ltms commented on issue fleet/fleetd#493 2026-09-12 05:53:50 +02:00
redeploy-fleetd.sh builds into the LIVE jar path, so the shutdown drain can die on a class it never loaded (#413)

Fixed and proven on a live redeploy. Closing.

Merged as #510 (aa4c0b8). The script no longer builds into the path the running daemon holds: it stages to target/fleetd-new.jar right after a…

ltms opened issue fleet/fleetd#512 2026-09-12 05:53:26 +02:00
redeploy-fleetd.sh says "no ERROR lines since restart" while blind to the exact failure #493 is about
ltms commented on issue fleet/fleetd#507 2026-09-12 05:52:23 +02:00
MessageServiceTest's coalescing tests sleep because the only observation available collects the ticket — the instrument is missing, not the test

Extra acceptance line: the shared instrument must itself be mutation-checked

This ticket and #506 are both fixed by the same instrument — a tick counter that MessageServiceTest:1671 can…

ltms opened issue fleet/fleetd#511 2026-09-12 05:48:58 +02:00
#493 follow-up: the drain-gate abort message names a recovery that does not work, and jar_id()'s default is unpinned
ltms commented on issue fleet/fleetd#509 2026-09-12 05:48:21 +02:00
#505 follow-up: the two-client completeness fold is unpinned, and legacyPrincipal can still re-open the escalation

Measured: this is a live bypass of #505's fix, not an independent gap

The fleet01 lead asked whether the two-client completeness fold is upstream of the predicate that #505's fix guards. If it…

ltms pushed to main at fleet/fleetd 2026-09-12 05:44:18 +02:00
aa4c0b84c3 Merge #510: never build into the path a running daemon holds (fleetd #493)
979adf82eb fleetd #493: never build into the path a running daemon holds
Compare 2 commits »
ltms merged pull request fleet/fleetd#510 2026-09-12 05:44:17 +02:00
fleetd #493: never build into the path a running daemon holds
ltms commented on issue fleet/fleetd#500 2026-09-12 05:37:23 +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

Correction: I attributed the detection to pipefail and that was wrong

In my comment above I wrote:

`producer missing at end of a pipe -> rc=5, DETECTED via pipefail (this script's real…

ltms closed issue fleet/fleetd#505 2026-09-12 05:36:17 +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