Cairn
NousResearch/hermes-agent

MCP SDK lazy-bind import errors handling and retry

Cluster 137438 · mcp. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These members appear to concern how errors during lazy binding of the MCP SDK are handled, including an issue describing them as swallowed into a misleading AttributeError and persisting for the process lifetime. The two pull requests propose surfacing broken imports and avoiding latching the unsuccessful bind, or retrying it; their outcomes are not stated in the titles.

Open issues1

  • Issue#137438Issue 2 — MCP SDK lazy-bind failures are swallowed into a misleading AttributeError and latched for the process lifetime

Open PRs2

  • PR#137440fix: retry failed MCP SDK lazy binding
  • PR#137447fix(tools): surface broken MCP SDK imports and stop latching the failed bind
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
mcp
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/137438.json
cluster/137438.md