• Joined on 2026-03-08
ltms created pull request fleet/fleetd#420 2026-09-10 06:27:28 +02:00
fleetd #416: fleet_list must enumerate the STARTUP profile set
ltms opened issue fleet/fleetd#418 2026-09-10 05:03:27 +02:00
Second instance of the #399 shape: a test uses Phase.ASKING as a barrier for push-loop state published later
ltms opened issue fleet/fleetd#417 2026-09-10 05:00:41 +02:00
Sweep for the REVERSE config mismatch: a boot snapshot read where the key is hot
ltms opened issue fleet/fleetd#416 2026-09-10 04:57:47 +02:00
fleet_list advertises free capacity for a profile the spawn gate refuses — CapacitySource reads the live profile keySet
ltms closed issue fleet/fleetd#409 2026-09-10 04:49:41 +02:00
The #399 completion-stamp race is verifiable deterministically — nowNanos is already injectable
ltms commented on issue fleet/fleetd#409 2026-09-10 04:49:36 +02:00
The #399 completion-stamp race is verifiable deterministically — nowNanos is already injectable

Merged as part of PR #414. Ruling on the contradiction the worker flagged: they were right, and the fault was in my brief.

The contradiction was mine, not a misreading

My ticket said two…

ltms merged pull request fleet/fleetd#414 2026-09-10 04:48:45 +02:00
fleetd #409: deterministic test for the #399 completion-stamp ordering race
ltms pushed to main at fleet/fleetd 2026-09-10 04:48:45 +02:00
4cd9046353 Merge pull request 'fleetd #409: deterministic test for the #399 completion-stamp ordering race' (#414) from worker/deterministic-stamp-race-409-3cb7b6-10 into main
4e98a74047 fleetd #409: deterministic test for the #399 completion-stamp ordering race
Compare 2 commits »
ltms commented on issue fleet/fleetd#395 2026-09-10 04:40:22 +02:00
A profile with no exhaustedPattern has usage-limit detection silently OFF — 6 of 8 live profiles, including both Claude subscription ones

Correction to this ticket's premise — the gap was never silence

I wrote that exhaustedPattern unset means detection is off "silently, with no warning at config load". That is false, and…

ltms opened issue fleet/fleetd#415 2026-09-10 04:40:02 +02:00
The startup coverage line reports "off" for errorPattern, but legacy classification is still running
ltms commented on issue fleet/fleetd#412 2026-09-10 04:39:05 +02:00
A daemon-side crash in the completion thread is silently misattributed to the worker

Cross-reference fix: the jar-rewrite trigger is #413, not #412. #412 is this ticket — I wrote the reference before the number was assigned.

The two are deliberately separate, and the split…

ltms opened issue fleet/fleetd#413 2026-09-10 04:38:56 +02:00
Building in the fleetd tree disarms the running daemon, and nothing warns at either end
ltms opened issue fleet/fleetd#412 2026-09-10 04:38:21 +02:00
A daemon-side crash in the completion thread is silently misattributed to the worker
ltms opened issue fleet/fleetd#411 2026-09-10 04:35:16 +02:00
Warn at load when two profiles share a tokenEnv but quarantine under different credential ids
ltms opened issue fleet/fleetd#410 2026-09-10 04:32:23 +02:00
liveStatus reported "working" for a member that did nothing for 76 minutes — the health snapshot has no progress signal
ltms commented on issue fleet/fleetd#409 2026-09-10 04:31:49 +02:00
The #399 completion-stamp race is verifiable deterministically — nowNanos is already injectable

Correction to this ticket's premise — a reproduction recipe now exists

Posted after the brief went out, so read this if you are working the ticket. Nothing in the goal, the constraints or…

ltms commented on issue fleet/fleetd#399 2026-09-10 04:31:21 +02:00
MessageServiceTest TTL test races the completedNanos stamp — passes on macOS, fails on Linux

Resolved: load is the axis, and the threshold is about 2x cores

The fleet01 lead ran the controlled experiment that settles this. One host, one commit, one command, with load as the only…

ltms opened issue fleet/fleetd#409 2026-09-10 04:27:34 +02:00
The #399 completion-stamp race is verifiable deterministically — nowNanos is already injectable
ltms closed issue fleet/fleetd#404 2026-09-10 04:21:58 +02:00
exhaustionDetectionArmed reads the LIVE config while detection reads the STARTUP snapshot — after a reload it reports armed when detection is still off
ltms closed issue fleet/fleetd#391 2026-09-10 04:21:39 +02:00
fleet_reply cannot answer a peer lead — the charter documents a path that does not exist