Cairn
NousResearch/hermes-agent

Cron job locking and cross-profile store isolation fixes

Cluster 61768. Data as of

Nothing open on GitHub. Fix merged in #61813. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #61813. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #61813. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs address race conditions in cron job handling, specifically missing lock acquisition during profile retargeting and cross-profile contamination of jobs.json stores. The work involves both locking fixes and isolating cron store paths by profile context.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #61813 fix(cron): isolate profile store paths by context

    merged to main

    files: cron/jobs.py, cron/scheduler.py, hermes_cli/web_server.py, tests/hermes_cli/test_web_server_cron_profiles.py

3 PRs closed without merging

From the close comments: superseded by another PR 2 · duplicate 1

  • #61818 fix(cron): isolate profile cron stores to stop cross-profile jobs.json overwrite · duplicate → #61813, #61768
  • #61906 fix(web_server): acquire cron.jobs _jobs_lock during _call_cron_for_profile retarget (#61768) · superseded by another PR → #61909, #61906
  • #61909 fix(web_server): acquire cron.jobs _jobs_lock during _call_cron_for_profile retarget (engine-on pilot, mirrors #61906) (#61768) · superseded by another PR → #61813, #61768, #61473, #61493
Closed issues · 1
  • Closed#61768Desktop serve backend: cron ticker thread races _call_cron_for_profile global retarget → destructive cross-profile jobs.json overwrite (full-store clone)
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.50: 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

Merged PRs
#61813
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
10 Jul 2026

For your agent

The same facts, typed.

cluster/61768.json
cluster/61768.md