ltms - Gitea

ltms opened issue fleet/fleetd#529

2026-09-12 07:27:43 +02:00

Tests pin shared logger levels and never restore them: 9 files, 19 pins, one proven cross-class collision — share SessionManagerTest's CapturedLog

ltms commented on issue fleet/fleetd#509

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

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

Both items are delivered, and I have now measured the part that was only a claim

The fleet01 lead asked a question that decides whether #505 is really closed: **is the two-client completeness…

ltms closed issue fleet/fleetd#525

2026-09-12 07:22:02 +02:00

A test pins the shared SessionManager logger to WARN and never restores it, so any later test asserting an INFO line silently sees nothing

ltms commented on issue fleet/fleetd#525

2026-09-12 07:21:56 +02:00

A test pins the shared SessionManager logger to WARN and never restores it, so any later test asserting an INFO line silently sees nothing

Merged as a6415f3 (PR #527). Closing.

Acceptance, as I measured it myself

Verified in my own worktree at the pushed head d8985719ebfd645afb6052279616d9ae3d368d65.

ltms commented on pull request fleet/fleetd#527

2026-09-12 07:20:59 +02:00

fleetd #525: restore the logger level, not just the appender, in SessionManagerTest

Correction to my own merge message: the first paragraph garbled the test file's hash into 0228f78424boa..., which is not a hash. The measured value, from shasum -a 256 on `fleetd/src/test/java/…

ltms merged pull request fleet/fleetd#527

2026-09-12 07:20:45 +02:00

fleetd #525: restore the logger level, not just the appender, in SessionManagerTest

ltms pushed to main at fleet/fleetd

2026-09-12 07:20:45 +02:00

a6415f3e52 Merge #527: restore the logger level, not just the appender, in SessionManagerTest (fleetd #525)

d8985719eb fleetd #525: restore the logger level, not just the appender, in SessionManagerTest

Compare 2 commits »

ltms commented on issue fleet/fleetd#518

2026-09-12 07:11:34 +02:00

Nothing tests that FleetMcp uses the CallerResolver — forcing the legacy identity path leaves the whole suite green at 1696/0

Closed by #524 (merged). Verified by my own build and my own mutations, not read off the PR body.

The fix section

ltms closed issue fleet/fleetd#518

2026-09-12 07:10:23 +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 07:10:23 +02:00

bb6fc9e0d7 Merge #524: FleetMcp's caller resolution is an explicit choice, and tested through the real transport (fleetd #518)

6a7342b1f0 fleetd #518: make the FleetMcp caller-resolution wiring an explicit choice, and test it once for real

Compare 2 commits »

ltms merged pull request fleet/fleetd#524

2026-09-12 07:10:22 +02:00

fleetd #518: FleetMcp caller resolution is an explicit choice, and tested for real

ltms closed issue fleet/fleetd#521

2026-09-12 07:03:29 +02:00

The swap guard can be disabled with the suite green — a "successful" redeploy that never puts the new jar in place

ltms commented on issue fleet/fleetd#521

2026-09-12 07:03:23 +02:00

The swap guard can be disabled with the suite green — a "successful" redeploy that never puts the new jar in place

Closed by #526 (merged). Ticked against this ticket's own fix and acceptance sections.

The fix section

ltms commented on issue fleet/fleetd#528

2026-09-12 07:02:55 +02:00

"Extract the decision so the suite can call it" pins the decision and never the wiring — drain_gate_refusal's call site can be bypassed with the suite green

Attribution correction to the ticket body above.

I wrote that I measured the call-site gap. I did, but #526's implementer found it first and reported it in that PR's body under "Caveat for…

ltms commented on pull request fleet/fleetd#526

2026-09-12 07:02:39 +02:00

fleetd #521: extract should_swap so the swap guard can't be silently disabled

Correction to my own merge message, which was unfair to the implementer.

I wrote that I measured the call-site gap. I did — but the implementer found it first and reported it, in this PR's…

ltms pushed to main at fleet/fleetd

2026-09-12 07:01:56 +02:00

3366590dbe Merge #526: pin the jar swap at its call site, not just its predicate (fleetd #521)

08771e270b fleetd #521 gate fix: pin the swap at the call site, not just the predicate

c89a375e5d fleetd #521: extract should_swap so the swap guard can't be silently disabled

Compare 3 commits »

ltms merged pull request fleet/fleetd#526

2026-09-12 07:01:55 +02:00

fleetd #521: extract should_swap so the swap guard can't be silently disabled

ltms opened issue fleet/fleetd#528

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

"Extract the decision so the suite can call it" pins the decision and never the wiring — drain_gate_refusal's call site can be bypassed with the suite green

ltms closed issue fleet/fleetd#519

2026-09-12 06:59:54 +02:00

probe-member-credentials.sh has no test harness at all, and its new arity message is off by one on an empty parse

ltms commented on issue fleet/fleetd#519

2026-09-12 06:59:47 +02:00

probe-member-credentials.sh has no test harness at all, and its new arity message is off by one on an empty parse

Closed by #523 (merged). Every item below was checked by me against the merged revision, not read off the PR body.

Item 1 — the harness

scripts/test-probe-member-credentials.sh added. 5…