Cairn
NousResearch/hermes-agent

macOS gateway cron owner fingerprint drift and start-time handling

Cluster 138216 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

One issue reports that on macOS the gateway's dead-owner reaper can mark a live hermes cron run execution as unknown when psutil's boot-time correction drifts beyond about 2 seconds. Two pull requests propose changes to how macOS owner fingerprints or start-time values are derived, including reading the kernel's creation time; their outcomes are not stated in the titles.

Open issues1

  • Issue#138216macOS: gateway dead-owner reaper marks a live `hermes cron run` execution `unknown` once psutil's boot-time correction drifts past 2 s

Open PRs1

  • PR#139895fix(gateway): read the kernel's creation time for macOS start-time fingerprints

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #138221 fix(gateway): stabilize macOS cron owner fingerprints · superseded by another PR → 26e7ecc, #128483, #138216
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
cron
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/138216.json
cluster/138216.md