Cairn
NousResearch/hermes-agent

Elevate MCP discovery failures from DEBUG to WARNING

Cluster 47509 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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 2 PRs.

Multiple issues and fixes address MCP discovery failures and missing SDK errors being logged at DEBUG level, making them invisible at default log settings. The proposed change promotes these log messages to WARNING level, optionally with install hints.

Open issues1

  • Issue#47509Gateway: MCP discovery failures logged at DEBUG, invisible at default log level

Open PRs2

  • PR#47520fix(gateway): log MCP discovery failures at WARNING, not DEBUG
  • PR#47623fix(gateway): log MCP discovery failures at WARNING instead of DEBUG

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #47602 fix(gateway): log MCP discovery failures at WARNING (#47509) · duplicate → #47520, #47509
  • #49438 fix(gateway): elevate MCP discovery failure from DEBUG to WARNING · other
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.40: 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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/47509.json
cluster/47509.md