Non-finite floats producing invalid JSON in tui_gateway RPC frames

NousResearch/hermes-agent · cluster 132800 · gateway

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

Members concern tui_gateway sending non-finite float values (e.g. bare Infinity) in RPC frames, notably in profiles.list when a profile.yaml ui_meta value is parsed by YAML as a float. Two titles describe proposed fixes to keep such values out of frames, and one describes the underlying problem.

Open issues1

  • Issue#132800tui_gateway: profiles.list sends bare Infinity (invalid JSON) when a profile.yaml ui_meta value is an unquoted id that YAML 1.1 reads as a float

Open PRs2

  • PR#125316fix(tui_gateway): keep non-finite YAML scalars out of the profiles.list frame
  • PR#132831fix(tui_gateway): keep non-finite floats out of RPC frames
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.67: 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
0 PRs closed without merging

For your agent

The same facts, typed.