Cairn
NousResearch/hermes-agent

Gateway run_sync UnboundLocalError on message variable

Cluster 5286 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 4 issues already closed.
Fix event
No fix has been merged to main. 4 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple reports and fix attempts targeting an UnboundLocalError caused by variable shadowing or a missing 'nonlocal' declaration for 'message' in the gateway's run_sync function. One member also bundles several unrelated community bugfixes alongside this issue.

Open issues0

No open issues.

Open PRs0

No open pull requests.

4 PRs closed without merging

From the close comments: done elsewhere 2 · PR volume cleanup 1 · superseded by another PR 1

  • #5276 fix(gateway): resolve UnboundLocalError in run_sync closure · superseded by another PR → #5290, #5326, #5286
  • #5287 fix(gateway): avoid shadowing run message · done elsewhere → 0c95e91, #5286
  • #5390 fix(gateway): resolve UnboundLocalError on message in run_sync · done elsewhere → 0c95e91, #5387
  • #37573 fix(gateway): avoid message shadowing in run_sync · PR volume cleanup
Closed issues · 4
  • Closed#5286bug: gateway _run_agent shadows message and breaks Codex path
  • Closed#5290fix: UnboundLocalError in gateway/run.py - add missing 'nonlocal message' declaration
  • Closed#5326Gateway crash in run_sync with UnboundLocalError on message after smart model routing change
  • Closed#5387fix(gateway): UnboundLocalError on 'message' in run_sync crashes every Telegram session
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: 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
4
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/5286.json
cluster/5286.md