NousResearch/hermes-agent
MCP HTTP timeout type fixes and multi-cron feature
Cluster 49629 · cron. Data as of
2 open items. Fix attempted, not merged.
The short answer
0open issues
2open PRs
6items grouped
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskSeveral members address a type mismatch where integer timeout values are passed instead of timedelta objects for MCP HTTP transports. One unrelated member adds support for multiple cron expressions per job.
Open issues0
Open PRs2
3 PRs closed without merging
From the close comments: duplicate 2 · superseded by another PR 1
-
#49648 fix(mcp): convert timeout values to timedelta for mcp >= 1.8.0 · duplicate →
#49646,#49629 -
#49721 fix(tools): convert MCP timeout values to timedelta for HTTP transports · superseded by another PR →
#49646 -
#49844 fix(mcp): pass HTTP timeout as timedelta on the deprecated client (#49629) · duplicate →
#49646
Closed issues · 1
- Closed#49629HTTP MCP timeout type mismatch: int passed where timedelta expected
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.33: 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
- cron
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging