Cairn
NousResearch/hermes-agent

Gateway memory monitor heartbeat not being started

Cluster 49773 · gateway. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

A bug where start_memory_monitoring() was never called from the gateway runtime, preventing the memory monitor heartbeat from running. Multiple fixes and a related periodic memory logging feature address this gap.

Open issues1

  • Issue#49773memory_monitor heartbeat never starts — start_memory_monitoring() not called from gateway runtime (v0.17.0)

Open PRs2

  • PR#49782fix(gateway): call start_memory_monitoring() from start_gateway()
  • PR#49789fix(gateway): start memory monitor heartbeat from runtime (#49773)

1 PR closed without merging

From the close comments: partial fix 1

  • #49837 fix(gateway): start the [MEMORY] heartbeat from the gateway runtime (#49773) · partial fix → a481ab0
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
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/49773.json
cluster/49773.md