mirror of
https://github.com/NousResearch/hermes-agent.git
synced 2026-07-26 17:38:36 +00:00
6179da5496
The sidebar strip and the Channels page could contradict each other on the same page load — "Gateway running" next to "The gateway is not running." /api/status and /api/messaging/platforms each open-coded their own liveness ladder: status probed GATEWAY_HEALTH_URL and scoped its PID/state reads to the requested profile, messaging did neither and used the uncached raw PID probe. Three deployments hit the split: a cross-container gateway (no local PID, only the health probe can see it), a profile-scoped dashboard (messaging borrowed a DIFFERENT profile's runtime state, reporting a false "connected" that hides a real outage — #71211), and a launch-service managed gateway with no PID file. Adds resolve_gateway_liveness() in gateway/status.py as the single ladder (cached PID -> HTTP health probe -> runtime-status PID with expected_home) and routes both endpoints, /api/messaging/platforms/{id}/test, and the kanban dispatcher-presence probe through it. Probe callables are injectable so the existing monkeypatch seams keep working, and GatewayLiveness.probe_error distinguishes "down" from "couldn't tell" so the kanban warning keeps failing OPEN instead of crying wolf. Closes #71211. |
||
|---|---|---|
| .. | ||
| browser | ||
| context_engine | ||
| cron_providers | ||
| dashboard_auth | ||
| disk-cleanup | ||
| google_meet | ||
| hermes-achievements | ||
| image_gen | ||
| kanban | ||
| memory | ||
| model-providers | ||
| observability | ||
| platforms | ||
| security-guidance | ||
| spotify | ||
| teams_pipeline | ||
| video_gen | ||
| web | ||
| __init__.py | ||
| plugin_utils.py | ||