Cron profile store path resolution timing fixes
NousResearch/hermes-agent · cluster 86519 · cron
Data as of
Nothing open on GitHub. Fix merged in #88337. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #88337. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #101245. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address cron job bugs around store paths being looked up at the wrong time or for the wrong profile, particularly in multiplex mode. Related concerns include UTC timestamps for claimed_at and run_claim clearance behavior for one-shot jobs on dispatch failure.
Open issues0
Open PRs0
Fixes on record
-
#88337 fix(cron): clear run_claim for one-shot jobs on dispatch failure (salvage #87591)
files:
cron/jobs.py,cron/scheduler.py,tests/cron/test_oneshot_dispatch_failure_run_claim.py -
#101245 fix(cron): multiplex ticks isolate per profile, fire the bound port, deliver satellites fail-closed (#74878 #100489 #101113 #86519, salvage #70747 #84755 #96944)
files:
cron/notepad.py,cron/scheduler.py,cron/scheduler_provider.py,cron/suggestions.py,hermes_cli/web_server.py,tests/cron/test_cron_multiplex_desktop_ticker_scope.py,tests/cron/test_cron_multiplex_shared_route_delivery.py,tests/cron/test_notepad.py,tests/cron/test_scheduler_provider.py,tests/cron/test_suggestions.py,tests/hermes_cli/test_cron_fire_dashboard.py,website/docs/user-guide/multi-profile-gateways.md
3 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1 · superseded by another PR 1
-
#87623 fix(cron): call-time store paths, UTC claimed_at, one-shot run_claim release · done elsewhere →
#86522,#88337,#87591 -
#96938 fix(cron): resolve profile store paths per call · superseded by another PR →
#96944 -
#96944 fix(cron): resolve profile store paths per call · merged via another change →
eed481b,#101245
Closed issues · 1
- Closed#86519cron: executions/notepad/suggestions resolve paths at import time — multiplex mode writes to the wrong profile's stores
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.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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