Skip to content

fix(dashboard): derive api Services latency_url from api_http_addr (closes #164)#165

Open
kiannidev wants to merge 1 commit into
GeniePod:mainfrom
kiannidev:fix/issue-164-dashboard-api-status-url
Open

fix(dashboard): derive api Services latency_url from api_http_addr (closes #164)#165
kiannidev wants to merge 1 commit into
GeniePod:mainfrom
kiannidev:fix/issue-164-dashboard-api-status-url

Conversation

@kiannidev
Copy link
Copy Markdown
Contributor

Summary

Closes #164

Real Behavior Proof

  • I have built and run the affected code locally (or noted why I could not).
  • I have verified the change end-to-end on Jetson hardware OR explained the equivalent verification path I used.

What I ran

cargo test -p genie-common api_status_url
cargo test -p genie-api dashboard_api_target
cargo fmt --all -- --check

What I observed

All tests passed. With [services.api].url = "127.0.0.1:4080/api/status", dashboard latency probe uses http://127.0.0.1:4080/api/status instead of the raw TOML string.

Test plan

  • cargo test -p genie-common api_status_url
  • cargo test -p genie-api dashboard_api_target dashboard_core_target
  • cargo fmt --all -- --check
  • Optional: dev TOML with custom API port, curl dashboard /api/services, api row healthy when genie-api listens

Add Config::api_status_url() and use it in dashboard_service_targets
so bare or stale [services.api].url values still probe the bound API.
Closes GeniePod#164
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[bug] dashboard: Services latency_url uses raw TOML instead of derived status URLs

1 participant