[hero_planner_server] no ping RPC method — connection-status reads 'backend down' #20

Closed
opened 2026-06-14 15:00:48 +00:00 by sameh-farouk · 1 comment
Member

The shared hero-connection-status component checks backend liveness via RPC method ping (a service convention — hero_proc's system domain and the hero_demo example both expose ping). hero_planner exposes system_health() instead, so the ping returns method-not-found and the dashboard reads "backend down" even when the backend is healthy.

Options: add a ping() to planner's oschema (convention), or align the shared indicator to a method planner exposes.

Screenshot_20260614_171159

The shared `hero-connection-status` component checks backend liveness via RPC method `ping` (a service convention — `hero_proc`'s `system` domain and the `hero_demo` example both expose `ping`). `hero_planner` exposes `system_health()` instead, so the ping returns method-not-found and the dashboard reads "backend down" even when the backend is healthy. Options: add a `ping()` to planner's oschema (convention), or align the shared indicator to a method planner exposes. ![Screenshot_20260614_171159](/attachments/b5ed5a9a-8e45-4785-bec7-43ad82a145d7)
Author
Member

Fixed on development in 7456769.

Added ping() -> bool to the main oschema service block + its impl (returns true), matching the hero_proc/hero_demo convention. The shared hero-connection-status indicator now reports the backend reachable (green). Regenerated openrpc_main.json + the sdk client — the service now exposes 98 methods.

Verified via the tunnel: indicator green, ping -> true.

Fixed on `development` in `7456769`. Added `ping() -> bool` to the `main` oschema service block + its impl (returns `true`), matching the `hero_proc`/`hero_demo` convention. The shared `hero-connection-status` indicator now reports the backend reachable (green). Regenerated `openrpc_main.json` + the sdk client — the service now exposes **98** methods. Verified via the tunnel: indicator green, `ping` -> `true`.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_planner#20
No description provided.