Cairn
NousResearch/hermes-agent

Handle Discord errors gracefully during shutdown

Cluster 21188 · gateway. 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.

These members address cases where Discord 403 or 503 responses during shutdown notifications can delay or disrupt clean exit. The fixes involve bounding notification sends with timeouts and handling these HTTP errors without blocking the shutdown process.

Open issues1

  • Issue#21188graceful_shutdown: Discord 403 during shutdown notification can delay clean exit

Open PRs1

  • PR#21339fix(gateway): bound shutdown notification sends with asyncio.wait_for

1 PR closed without merging

From the close comments: done elsewhere 1

  • #21199 fix(gateway): handle Discord 403/503 in send() gracefully during shutdown · done elsewhere → cc8e5ec, #35647
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
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/21188.json
cluster/21188.md