MCP schema cache ttl_ms=0 lazy mode bug fix
NousResearch/hermes-agent · cluster 101007 · mcp
Data as of
3 open items. Fix attempted, not merged.
The short answer
1open issue
2open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug where ttl_ms of 0 in MCP schema cache entries was treated as expired rather than as no TTL hint, preventing lazy mode from engaging. The fix reinterprets ttl_ms=0 as the absence of a hint.
Open issues1
- Issue#101007`mcp_servers.<name>.lazy` never engages: schema cache entries written with `ttl_ms: 0` are treated as expired
Open PRs2
1 PR closed without merging
From the close comments: duplicate 1
-
#101390 fix(tools): treat ttl_ms=0 as no TTL hint in MCP schema cache (#101007) · duplicate →
#92621
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
- Subsystem
- mcp
- Closed issues
- 0
- Attempts
- 1 PR closed without merging