diff options
| author | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-05-16 12:56:24 -0400 |
|---|---|---|
| committer | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-05-16 12:56:24 -0400 |
| commit | 43c62c2f338654394f82c86aa12b22be6a358d94 (patch) | |
| tree | f2774b2e91fe029f612d267899c8c01057168e46 /CHANGELOG.md | |
| parent | 2ac665ec31fe156b372540e8ac38aa42765b3001 (diff) | |
0.17.1: fix /chrome onboard stuck on 'Waiting for the extension to wake up'
0.17.0 made the daemon own the HTTP listener, but the Pi client's
bridge.status().connected still reflected the local Pi's lastSeenAt
(which is never updated in the daemon model). Onboard's connect-wait
loop spun forever even when the extension was polling the daemon.
Fix: new ChromeProfileBridge.daemonStatus() async helper that fetches
the daemon's /status. onboard, doctor, and status now query that for
the 'connected' flag instead of reading stale Pi-side state.
Diffstat (limited to 'CHANGELOG.md')
| -rw-r--r-- | CHANGELOG.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md index 99af471..5f2fed8 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,20 @@ All notable user-facing changes to `pi-chrome`. +## 0.17.1 — 2026-05-16 + +### Fix: `/chrome onboard` stuck on "Waiting for the extension to wake up…" + +0.17.0 made the daemon (not the Pi process) own the HTTP listener, but the Pi client's +`bridge.status().connected` still reflected the *local Pi*'s `lastSeenAt`, which never gets +updated in the daemon model. Result: onboard's connect-wait loop spun forever even when the +extension was happily polling the daemon. + +- New `ChromeProfileBridge.daemonStatus()` async method: fetches the daemon's `/status` and + returns its view (the only correct source of truth in 0.17+). +- `/chrome onboard`, `/chrome doctor`, `/chrome status` now query `daemonStatus()` for the + `connected` flag instead of reading stale Pi-side `lastSeenAt`. + ## 0.17.0 — 2026-05-16 ### Standalone daemon (no more owner-vs-client topology) |