fleet/fleetd
3
0
Fork 0
Code Issues 73 Pull Requests Actions Packages Projects Releases 1 Wiki Activity

CB-573: add dormant fleet health monitor #47

Closed
agent wants to merge 1 commits from worker/cb573b-3db06f-16 into main
pull from: worker/cb573b-3db06f-16
merge into: fleet:main
Conversation 1 Commits 1 Files Changed 7
+40 -14
agent commented 2026-08-15 06:10:59 +02:00
Member
Copy Link
Copy Source

Adds the opt-in whole-fleet health scheduler, health config, and bridge_list health coverage. Tests: mvn -f bridged/pom.xml clean install (674 tests, BUILD SUCCESS).

Adds the opt-in whole-fleet health scheduler, health config, and bridge_list health coverage. Tests: mvn -f bridged/pom.xml clean install (674 tests, BUILD SUCCESS).
ltms added 2 commits 2026-08-15 06:17:31 +02:00
CB-573: add dormant fleet health monitor 826fffe05b
CB-573: keep health monitoring after failures
CI / contract (pull_request) Successful in 42s
Details
CI / build (pull_request) Successful in 1m15s
Details
c76b2f149e
ltms force-pushed worker/cb573b-3db06f-16 from bcee1f9581 to c76b2f149e 2026-08-15 06:17:31 +02:00 Compare
ltms added 1 commit 2026-08-15 06:27:42 +02:00
CB-573: carry accepted turn tokens on delivery
CI / contract (pull_request) Failing after 40s
Details
CI / build (pull_request) Failing after 1m9s
Details
38f13f4b3c
ltms commented 2026-08-15 07:12:39 +02:00
Owner
Copy Link
Copy Source

Closing as landed — main has b745e15, same title.

This one needed the extra check, because git cherry main worker/cb573b-3db06f-16 reported the commit 38f13f4 as not present by patch-id. That turned out to be a rebase artefact, not lost work. Two pieces of evidence:

  1. Identical file stat — both 38f13f4 and b745e15 change the same 7 files, 40 insertions(+), 14 deletions(-).
  2. git diff main origin/worker/cb573b-3db06f-16 -- <those 7 files> is empty. main already holds byte-identical content.

The patch-id differs only because the commit was replayed onto a different parent. No code is lost. Verified 2026-08-15.

Closing as **landed** — `main` has `b745e15`, same title. This one needed the extra check, because `git cherry main worker/cb573b-3db06f-16` reported the commit `38f13f4` as **not** present by patch-id. That turned out to be a rebase artefact, not lost work. Two pieces of evidence: 1. Identical file stat — both `38f13f4` and `b745e15` change the same 7 files, `40 insertions(+), 14 deletions(-)`. 2. `git diff main origin/worker/cb573b-3db06f-16 -- <those 7 files>` is **empty**. `main` already holds byte-identical content. The patch-id differs only because the commit was replayed onto a different parent. No code is lost. Verified 2026-08-15.
ltms closed this pull request 2026-08-15 07:12:41 +02:00
Some checks are pending
CI / contract (pull_request) Failing after 40s
Details
CI / build (pull_request) Failing after 1m9s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
blocked
Cannot start until something else lands. The body says what.
 needs-live-proof
Merged and green, but never shown working on the running daemon. Not the same as done.
 ready-to-delegate
Scope, files and acceptance criteria are written. A worker can be briefed from the body alone.
 silent-default
A feature that compiles, passes tests, and ships turned off. Nine recurrences and counting.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent kevin ltms
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: fleet/fleetd#47
Delete Branch "worker/cb573b-3db06f-16"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?