Block a user
A timed-out
git worktree add leaks the worktree it half-created: #274's cleanup does not cover the add itself
A worker spawned during the shutdown drain is never drained: its pane is left running and its worktree is never preserved
A worker spawned during the shutdown drain is never drained: its pane is left running and its worktree is never preserved
Merged to main in 8beae50.
What I checked myself
The two mechanisms are independently covered. The worker's own mutation reverted all of SessionManager.java, which proves the pair…
A timed-out
git worktree add leaks the worktree it half-created: #274's cleanup does not cover the add itself
Merged to main in b2a58cb.
What I checked myself
The fix introduced a data-loss path, and the worker found it and guarded it. This was not in my ticket. Moving git worktree add…
#310: prevent idle reap from stopping delivered workers
reapIdle can release a session that just became BUSY, contradicting its own documented invariant
reapIdle can release a session that just became BUSY, contradicting its own documented invariant
Merged as a49671c, with one addition of mine in f159ca7. Both on main.
The design is right
registry.remove(paneId, expected) is ConcurrentHashMap's compare-and-remove, and it is the…
reapIdle can release a session that just became BUSY, contradicting its own documented invariant
A timed-out
git worktree add leaks the worktree it half-created: #274's cleanup does not cover the add itself
A worker spawned during the shutdown drain is never drained: its pane is left running and its worktree is never preserved
A worker's report is stranded when its fleet_ask timed out, and the lead is told the worker never replied
A worker that wedges in unknown during post-turn housekeeping is polled forever and can never be delivered to again
Fixed in 76672ff, on main.
Mutation proof
Reverted only Injector.java, kept the three new tests:
[ERROR] Tests run: 30, Failures: 2 -- in dev.ltms.fleet.inject.InjectorTest
Assertio…
A worker that wedges in unknown during post-turn housekeeping is polled forever and can never be delivered to again
A worker that wedges in unknown during post-turn housekeeping is polled forever and can never be delivered to again
A worker connecting from 127.0.0.2 is resolved as the primary, and gains spawn/stop/send/drain
Fixed in 9379f92, on main.
Mutation proof
Reverted only the two source files (git apply -R), kept the tests. The failure text states the escalation better than prose can:
[ERROR]…
A worker connecting from 127.0.0.2 is resolved as the primary, and gains spawn/stop/send/drain