Gateway lock ownership and cron liveness fixes
Cluster 18631 · cron. Data as of
1 open item. Fix merged in #106516 on 9 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 0 issues already closed.
- Fix event
- A fix was merged to main in PR #106516. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read #106516, then check whether your report is the one still open.
Read #106516Pick up a Lab taskThese members address bugs and regression coverage around shared runtime lock ownership in the gateway and how the cron/builtin-ticker subsystem trusts that lock to determine liveness. A recurring concern is preventing scoped status polls from incorrectly deleting or overwriting a live foreign gateway's pid or lock state.
Open issues1
- Issue#18631Add CLI-level regression coverage for shared-lock cron status
Open PRs0
Fixes on record
-
#96214 fix(cron): trust the gateway runtime lock for builtin-ticker liveness (salvage #95947)
files:
contributors/emails/[redacted:email],hermes_cli/cron.py,tests/cron/test_87033_cronjob_gateway_liveness.py -
#106516 fix(gateway): scoped profile status polls no longer delete a live foreign gateway's pid/lock (#106406, salvage #106454 #104113)
files:
gateway/status.py,tests/gateway/test_status.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#79566 fix(gateway): preserve shared runtime lock ownership · superseded by another PR →
#96214,#106516
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.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