Cairn
NousResearch/hermes-agent

Signal JSON-RPC response body size limits

Cluster 55025 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue 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 1 PR.

These issues and pull requests concern unbounded body reads when handling Signal JSON-RPC responses, along with related compatibility work for signal-cli-rest-api v0.99 REST and WebSocket support.

Open issues1

  • Issue#55025Signal JSON-RPC responses are read without a body cap

Open PRs1

  • PR#55026fix(signal): bound JSON-RPC response reads

1 PR closed without merging

From the close comments: duplicate 1

  • #55249 fix: add body cap to Signal JSON-RPC responses · duplicate → #55026
Closed issues · 1
  • Closed#55237Signal RPC reads unbounded response bodies
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.39: 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
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/55025.json
cluster/55025.md