NousResearch/hermes-agent

Gateway config flag using json instead of yaml

Cluster 10216 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 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
Nothing open on GitHub.

Multiple reports and fixes addressing the gateway incorrectly using json.load instead of yaml.safe_load when parsing the --config flag or config file. One entry also mentions a MessageDeduplicator TTL enforcement change alongside the yaml fix.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: done elsewhere 1 · other 2

  • #7244 fix(gateway): use yaml.safe_load instead of json.load when parsing gateway config file · done elsewhere → 2edbf15, #10216
  • #10236 fix(gateway): use yaml.safe_load instead of json.load for --config flag · other
  • #10289 fix(gateway): use yaml.safe_load for config file parsing · other
Closed issues · 1
  • Closed#10216[Bug]: Gateway fails to start with `--config` flag: `json.load()` used instead of `yaml.safe_load()`
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.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
3 PRs closed without merging

For your agent

The same facts, typed.