TUI WebSocket send backlog bounding fixes

NousResearch/hermes-agent · cluster 108147 · 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.

A bug report and multiple fix attempts addressing unbounded accumulation of WebSocket send batches in the TUI, which could cause unbounded heap retention. The members represent iterative or competing patch efforts for the same issue.

Open issues1

  • Issue#108147[Bug]: TUI WebSocket send batches accumulate without a byte or frame bound

Open PRs2

  • PR#108154fix(tui): bound WebSocket send backlog
  • PR#108155fix(tui): bound WSTransport backlog to prevent unbounded heap retention

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #108151 [superseded by #108154/#108155] fix(tui): bound WebSocket send backlog · superseded by another PR → #108202, #108147
  • #108202 fix(tui): bound WebSocket send backlog · superseded by another PR → #108151, #108147, #108154, #108155
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.