NousResearch/hermes-agent

Gateway drain and restart timing edge cases

Cluster 82161 · gateway. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #86684 on 15 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #86684, then check it covers your case.

Read #86684 Pick up a Lab task

These items concern bugs in gateway shutdown behavior, specifically around drain timeout zero not waiting for in-flight work and a deadlock risk during gateway-owned restarts.

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.

#86684 fix(gateway): drain floor for in-flight cron + interrupted-cron notices before adapter disconnect

merged to main

files: cli-config.yaml.example, cron/scheduler.py, gateway/restart.py, gateway/run.py, hermes_cli/config_defaults.py, tests/gateway/restart_test_helpers.py, tests/gateway/test_cron_active_work_drain.py, tests/gateway/test_cron_drain_floor.py, tests/gateway/test_cron_interrupt_notification.py, tests/gateway/test_shutdown_cache_cleanup.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

#82195 fix(update): avoid gateway-owned restart deadlock · superseded by another PR → #82279, #82161, #82195, #82224, #82244
#82282 fix(gateway): drain timeout=0 must still wait for in-flight cron/API work · merged via another change → #86684, #82224

Closed issues · 1

Closed#82161Gateway drain exits after 0.00s with in-flight cron job, killing it mid-run

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

Subsystem: gateway
Merged PRs: #86684
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 15 Aug 2026

For your agent

The same facts, typed.

cluster/82161.json
cluster/82161.md