docs: BUG-11 closed — GPS lat/lon from API, 30s staleness aligned across pages
This commit is contained in:
@@ -44,23 +44,6 @@ When CLOSED, move the entire entry to Resolved — don't duplicate.
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
### BUG-11 — Dashboard GPS shows "Stale fix" while Status shows "Live fix"
|
|
||||||
- **Status**: `OPEN`
|
|
||||||
- **Severity**: Low
|
|
||||||
- **Area**: `static/js/yaris.js`, `static/js/status.js`
|
|
||||||
- **Phase**: Phase 26
|
|
||||||
- **Symptom**: Dashboard shows "Stale fix", lat/lon blank. Status page shows "Live fix"
|
|
||||||
with valid coordinates. Both pages query the same `/api/gps/status` endpoint.
|
|
||||||
- **Root cause**: Dashboard `renderGpsStatus()` updates badge + age text but never
|
|
||||||
populates lat/lon fields — those only receive data from the live `socket.on('gps_location')`
|
|
||||||
event. Status page reads `gps.latitude`/`gps.longitude` directly from the API response.
|
|
||||||
Also, the staleness thresholds differ: Dashboard marks stale at >30s, Status page
|
|
||||||
ignores age entirely.
|
|
||||||
- **Fix scope**: `renderGpsStatus()` should populate lat/lon from the API response
|
|
||||||
(already present in `status.latitude`, `status.longitude`).
|
|
||||||
- **Acceptance**: Dashboard GPS card matches Status page — both show same fix status
|
|
||||||
and coordinates.
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## Resolved
|
## Resolved
|
||||||
@@ -85,6 +68,16 @@ When CLOSED, move the entire entry to Resolved — don't duplicate.
|
|||||||
- **Fix**: `"obd" if speed > 0 else "gps"` matching Pi logic.
|
- **Fix**: `"obd" if speed > 0 else "gps"` matching Pi logic.
|
||||||
- **Verification**: Docker rebuild, `/health` OK LAN + Cloudflare.
|
- **Verification**: Docker rebuild, `/health` OK LAN + Cloudflare.
|
||||||
|
|
||||||
|
### BUG-11 — Dashboard GPS shows "Stale fix" while Status shows "Live fix"
|
||||||
|
- **Status**: `CLOSED` 2026-08-11
|
||||||
|
- **Commit**: `9733036`
|
||||||
|
- **Fix**: `renderGpsStatus()` now reads `status.latitude`/`status.longitude` from
|
||||||
|
the `/api/gps/status` response (not just socket events). Status page now uses the
|
||||||
|
same 30s staleness threshold (`fix_age_seconds > 30` → "Stale fix") instead of
|
||||||
|
calling any fix "Live" regardless of age.
|
||||||
|
- **Verification**: Deployed to Pi, dashboard GPS card now shows lat/lon coordinates
|
||||||
|
even when fix is stale. Both pages agree on fix status.
|
||||||
|
|
||||||
### BUG-07 — Trip replay on portal sometimes does nothing
|
### BUG-07 — Trip replay on portal sometimes does nothing
|
||||||
- **Status**: `CLOSED` 2026-08-11
|
- **Status**: `CLOSED` 2026-08-11
|
||||||
- **Commit**: `fa93384`
|
- **Commit**: `fa93384`
|
||||||
|
|||||||
@@ -1860,7 +1860,7 @@ phase roadmap.
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
### Phase 26: Road-test bug fixes — 🚧 IN PROGRESS (8 closed, 1 open, 1 hardware)
|
### Phase 26: Road-test bug fixes — 🚧 IN PROGRESS (9 closed, 1 deployed awaiting test, 1 hardware)
|
||||||
**Last updated 2026-08-11.** Targeted bug-fix pass for defects surfaced by the Phase 25 in-car
|
**Last updated 2026-08-11.** Targeted bug-fix pass for defects surfaced by the Phase 25 in-car
|
||||||
road test. Each item tracked in [BUGS.md](./BUGS.md).
|
road test. Each item tracked in [BUGS.md](./BUGS.md).
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user