tegwick
8e36b22e26
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a053ff-1d6f-7fe2-ac1c-a6eb40a42a0c
34 lines
1 KiB
Markdown
34 lines
1 KiB
Markdown
---
|
|
id: STATE-WP-ADHOC-2026-06-04
|
|
type: workplan
|
|
title: "Ad hoc fixes - 2026-06-04"
|
|
domain: custodian
|
|
repo: state-hub
|
|
status: finished
|
|
owner: codex
|
|
topic_slug: custodian
|
|
created: "2026-06-04"
|
|
updated: "2026-06-04"
|
|
state_hub_workstream_id: "b13e38a7-8623-5a31-b6b0-3d94d42afcd6"
|
|
---
|
|
|
|
# Ad hoc fixes - 2026-06-04
|
|
|
|
## Fix Dashboard Overview API Loading
|
|
|
|
```task
|
|
id: STATE-WP-ADHOC-2026-06-04-T01
|
|
status: done
|
|
priority: high
|
|
state_hub_task_id: "ef58247a-24c2-5362-a851-adb31c747abf"
|
|
```
|
|
|
|
The overview page reported `Dashboard data load failed: NetworkError when
|
|
attempting to fetch resource.` even when the API was healthy from Windows.
|
|
The root cause was brittle browser/API connection setup: the dashboard assumed
|
|
`http://127.0.0.1:8000`, while the API CORS defaults allowed only the exact
|
|
dashboard origins on port 3000.
|
|
|
|
Result: the dashboard now resolves its API base from the current browser host
|
|
with explicit query/storage/global overrides, and the API allows common local
|
|
Observable dashboard origins on ports 3000-3005, including IPv6 loopback.
|