Relay managed execution async event-loop conflict fixes
Cluster 77244. Data as of
Nothing open on GitHub. Fix merged in #82313 on 9 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #82313. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #82313. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and pull requests address a bug where NeMo Relay's managed execution wraps async tools that have persistent event loops, causing 'Future attached to different loop' errors. Multiple fix approaches are represented, including bypassing managed execution for nested calls and for tools with persistent loops.
Open issues0
Open PRs0
Fixes on record
-
#82313 fix(relay): bypass managed execution for nested calls inside managed callbacks
files:
agent/relay_llm.py,agent/relay_runtime.py,agent/relay_tools.py,tests/agent/test_relay_nested_execution.py
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#77244[Bug] NeMo Relay retain_managed_execution causes Future attached to different loop for async tools like vision_analyze
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 LabAt a glance
- Merged PRs
- #82313
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 9 Aug 2026