NousResearch/hermes-agent

Relay concurrent-turn scope-handle race and close fix

Cluster 115471. Data as of 2026-10-26 12:29 UTC

Nothing open on GitHub. Fix merged in #116685 on 20 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #116685 Pick up a Lab task

These items address a race condition in relay/telemetry where concurrent turns cause a 'scope handle is not at the top of the stack' error during task close, and a related issue where failing session pushes are not retried. The work involves bounding task scope drain and making concurrent turn close safer.

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.

#116685 fix(relay): a failing session push is not retried and concurrent-turn task close no longer raises 'not at the top of the stack' (#115528, #115471, salvage #115531)

merged to main

files: agent/relay_runtime.py, hermes_cli/observability/relay_shared_metrics.py, tests/agent/test_relay_session_segments.py, tests/hermes_cli/test_relay_shared_metrics_runtime.py

1 PR closed without merging

From the close comments: done elsewhere 1

#115498 fix(telemetry): bounded task scope drain and safe concurrent turn close (#115471) · done elsewhere → 148d1f6, #116685, #115528, #115471, #115531

Closed issues · 1

Closed#115471Relay scope-handle race on concurrent turns: 'scope handle is not at the top of the stack' in shared-metrics close path

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

Merged PRs: #116685
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/115471.json
cluster/115471.md