service.toml is missing [[env]] PATH_ROOT block, panics when supervised by hero_proc #110

Closed
opened 2026-05-23 03:33:11 +00:00 by mik-tf · 2 comments
Owner

When hero_router is launched through hero_proc (rather than directly with the env preloaded), it panics with 'PATH_ROOT is not set' because its service.toml does not include the env blocks that propagate PATH_ROOT / PATH_VAR / PATH_BUILD / PATH_CODE / HERO_SOCKET_DIR from the supervisor. The fix matches the pattern in hero_assistance / hero_proc_admin / hero_cockpit / hero_proc itself: add the canonical env entries in service.toml.

When hero_router is launched through hero_proc (rather than directly with the env preloaded), it panics with 'PATH_ROOT is not set' because its service.toml does not include the [[env]] blocks that propagate PATH_ROOT / PATH_VAR / PATH_BUILD / PATH_CODE / HERO_SOCKET_DIR from the supervisor. The fix matches the pattern in hero_assistance / hero_proc_admin / hero_cockpit / hero_proc itself: add the canonical [[env]] entries in service.toml.
Author
Owner

Fixed in 175fff0 on development. Appended PATH_ROOT, HERO_SOCKET_DIR, and RUST_LOG [[env]] blocks to crates/hero_router/service.toml matching the canonical 3-entry pattern from hero_cockpit_server/service.toml. Verified live: lab service hero_router --install --start re-registers the action spec, supervised launch binds 127.0.0.1:9988, /health returns 200, all six lab smoke tests pass.

Fixed in [`175fff0`](https://forge.ourworld.tf/lhumina_code/hero_router/commit/175fff0e12cecdc22ff4e107c724b0a5b5139e8c) on `development`. Appended PATH_ROOT, HERO_SOCKET_DIR, and RUST_LOG `[[env]]` blocks to `crates/hero_router/service.toml` matching the canonical 3-entry pattern from `hero_cockpit_server/service.toml`. Verified live: lab service hero_router --install --start re-registers the action spec, supervised launch binds 127.0.0.1:9988, /health returns 200, all six lab smoke tests pass.
Author
Owner

Followup note for the record: this same service.toml [[env]] gap was independently rediscovered yesterday (2026-05-22) from the supervised hero_router launch path, hit the canonical Lesson 17 trap, and was fixed today (2026-05-23) with the same 3-entry [[env]] block (PATH_ROOT, HERO_SOCKET_DIR, RUST_LOG). Same root cause from two different code paths (this issue caught it from hero_assistance smoke through the router on the customer side; the other path caught it from the supervised launch silent panic on the operator side), same fix. Logging the convergence so future readers can find the matched-fix pair.

Followup note for the record: this same `service.toml` `[[env]]` gap was independently rediscovered yesterday (2026-05-22) from the supervised hero_router launch path, hit the canonical Lesson 17 trap, and was fixed today (2026-05-23) with the same 3-entry `[[env]]` block (`PATH_ROOT`, `HERO_SOCKET_DIR`, `RUST_LOG`). Same root cause from two different code paths (this issue caught it from `hero_assistance` smoke through the router on the customer side; the other path caught it from the supervised launch silent panic on the operator side), same fix. Logging the convergence so future readers can find the matched-fix pair.
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_router#110
No description provided.