Dashboard backend unreachability detection and error handling

NousResearch/hermes-agent · cluster 50270 · dashboard

Data as of

3 open items. Fix attempted, not merged.

The short answer

2open issues
1open PR
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
2 issues and 1 PR. Broad area: open items may be separate problems.

These members address the failure to detect and surface when the dashboard backend is unreachable, covering a swallowed network error in fetchJSON, a stale 'Running' status shown in the sidebar, and a fix to warn users when the backend cannot be reached.

Open issues2

  • Issue#50270[Bug]: Dashboard sidebar keeps showing 'Gateway Status: Running' after backend dies
  • Issue#53719fetchJSON swallows network failures with generic TypeError; should throw structured DASHBOARD_UNREACHABLE error

Open PRs1

  • PR#50290fix(web): warn when dashboard backend is unreachable
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: 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.