Cairn
NousResearch/hermes-agent

/api/status health fallback deadline handling in executor exit

Cluster 138388 · dashboard. 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.

One bug report says the /api/status one-second health fallback waits beyond its deadline during executor __exit__. Two fix-titled pull requests, one for the dashboard and one for the CLI, both aim to return the fallback at its deadline. The titles alone do not show whether either change is merged or effective.

Open issues1

  • Issue#138388[Bug]: /api/status one-second health fallback waits past its deadline in executor __exit__

Open PRs2

  • PR#138399fix(cli): return the /api/status health fallback at its route deadline
  • PR#138400fix(dashboard): return the /api/status health fallback at its deadline
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
dashboard
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/138388.json
cluster/138388.md