ltms - Gitea

ltms commented on issue fleet/fleetd#137

2026-08-31 09:28:14 +02:00

CB-629: after a bridge_ask round-trip, the worker's final reply orphans its ticket, which then reports a false failure

Fixed and merged to main as 388aba7. Closing.

The hypothesis in this ticket was close, but the real cause is narrower

This ticket guessed that the fleet_ask reverse rendezvous detaches…

ltms commented on issue fleet/fleetd#172

2026-08-31 09:27:51 +02:00

LAVINMQ_URI reaches every member pane with the broker password inline — on neither credential list, and not credential-shaped

Fixed and merged to main as ad587ea. Closed — with one honest limit recorded below.

What shipped

The exclusion is derived from the config, not hand-typed: whatever broker.uriEnv…

ltms closed issue fleet/fleetd#137

2026-08-31 09:27:34 +02:00

CB-629: after a bridge_ask round-trip, the worker's final reply orphans its ticket, which then reports a false failure

ltms closed issue fleet/fleetd#172

2026-08-31 09:27:33 +02:00

LAVINMQ_URI reaches every member pane with the broker password inline — on neither credential list, and not credential-shaped

ltms closed issue fleet/fleetd#161

2026-08-31 09:27:32 +02:00

a pane member's grandchild process may be resolved as primary — possible worker→primary escalation

ltms commented on issue fleet/fleetd#161

2026-08-31 09:27:21 +02:00

a pane member's grandchild process may be resolved as primary — possible worker→primary escalation

Fixed and merged to main as 08ce9ae. Closing.

The unconfirmed half is now settled

This ticket said the daemon-side behaviour was confirmed (no pane ⇒ primary) but the worker-can-trigger-i…

ltms commented on pull request fleet/fleetd#203

2026-08-31 09:26:36 +02:00

CB-175: quarantine opencode model mismatches

Holding this one — not merging yet. The code is well built, but I believe the check can never fire in production. That is not a criticism of the work: you flagged that you could not test end…

ltms opened issue fleet/fleetd#206

2026-08-31 09:26:10 +02:00

opencode session discovery never finds a member's record, so agentSessionId is always null and resume silently does nothing

ltms pushed to main at fleet/fleetd

2026-08-31 09:25:41 +02:00

388aba7632 #137: an answered turn's reply completes its own ticket, instead of a false failure

ltms pushed to main at fleet/fleetd

2026-08-31 09:22:38 +02:00

ad587eafa3 #172: keep the broker URI, password and all, out of every member pane

ltms pushed to main at fleet/fleetd

2026-08-31 09:16:59 +02:00

08ce9aef11 #161: resolve a pane by process ancestry, closing a worker->primary escalation

ltms commented on issue fleet/fleetd#145

2026-08-31 09:00:36 +02:00

CB-632: purge "bridge" from the code, the artefacts and the ops surface

Audit against main at 4ac688b. The purge is complete except for three deliberate retentions, which I am listing rather than closing over, because each is a decision and not an oversight.

`…

ltms closed issue fleet/fleetd#126

2026-08-31 09:00:14 +02:00

CB-622: rename the MCP tool namespace bridge_* -> fleet_*, with one dual-name release

ltms commented on issue fleet/fleetd#126

2026-08-31 09:00:08 +02:00

CB-622: rename the MCP tool namespace bridge_* -> fleet_*, with one dual-name release

Done, and the dual-name window has already closed. Closing.

Checked against main at 4ac688b:

$ grep -rn "bridge_" fleetd/src/main/java --include='*.java'

ltms opened issue fleet/fleetd#201

2026-08-31 05:57:59 +02:00

Backend-error classification needs a real mechanism, not hard-coded strings (#164 points 3 and 4)

ltms closed issue fleet/fleetd#164

2026-08-31 05:57:32 +02:00

a member whose backend 400s dies in one second, and fleetd returns the lost turn as a successful empty reply

ltms commented on issue fleet/fleetd#164

2026-08-31 05:57:28 +02:00

a member whose backend 400s dies in one second, and fleetd returns the lost turn as a successful empty reply

Points 1 and 2 are done and on main. Closing.

ltms commented on pull request fleet/fleetd#200

2026-08-31 05:57:07 +02:00

#164: classify a backend-error scrape as WORKER_FAILED, not a completed reply

Merged to main as 4ac688b (squashed). Thanks — the staleness catch was the valuable part of this run.

What I checked myself, and how

I did not take the "already on main" claim on trust,…

ltms pushed to main at fleet/fleetd

2026-08-31 05:56:49 +02:00

4ac688b6d9 #164: classify a backend-error scrape as WORKER_FAILED, carrying the whole pane

ltms opened issue fleet/fleetd#199

2026-08-31 05:50:23 +02:00

GET /members returns its rows under a "workers" key, so a caller reading "members" sees an empty fleet