diff options
| author | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-05-16 13:00:48 -0400 |
|---|---|---|
| committer | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-05-16 13:00:48 -0400 |
| commit | fcae5b188baa1bdfed48208d7cfc2b711af4aae3 (patch) | |
| tree | 040c6cde8b8d23d1909c7235641e6694ed170495 /extensions/chrome-profile-bridge/index.ts | |
| parent | 43c62c2f338654394f82c86aa12b22be6a358d94 (diff) | |
0.17.2: fix /next lastSeenAt + strict daemon version match
Bugs surfaced in real-world 0.17.0/0.17.1 testing:
1. Daemon /next only recorded lastSeenAt AFTER the auth/pair checks. Pre-pair
the daemon returns needsPairing early without recording the poll, so
connected stayed false even though the extension was polling. /chrome
onboard's wait-for-poll loop spun forever on a healthy extension.
Fix: record lastSeenAt at the top of /next for any chrome-extension
origin, before auth checks. Onboard now correctly detects 'extension
alive but unpaired' which is the precise state during pair step.
2. Daemon compatibility was checked at major.minor match. Result: a patch
release fixing a daemon bug (like #1) couldn't replace the running
daemon — new Pi client joins old buggy daemon as client.
Fix: exact version match. Patch releases auto-kill+respawn the daemon.
Diffstat (limited to 'extensions/chrome-profile-bridge/index.ts')
| -rw-r--r-- | extensions/chrome-profile-bridge/index.ts | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/extensions/chrome-profile-bridge/index.ts b/extensions/chrome-profile-bridge/index.ts index db41ce3..820c7d7 100644 --- a/extensions/chrome-profile-bridge/index.ts +++ b/extensions/chrome-profile-bridge/index.ts @@ -114,10 +114,12 @@ function probeBridgeStatus(host: string, port: number): { bridgeVersion?: string } } -function sameMajorMinor(a: string, b: string): boolean { - const [aMaj, aMin] = a.split(".").map((n) => Number(n)); - const [bMaj, bMin] = b.split(".").map((n) => Number(n)); - return aMaj === bMaj && aMin === bMin; +// Daemon compat is checked at exact version match — not major.minor — so that even patch +// releases trigger an automatic kill+respawn. Patch releases routinely fix bugs in the daemon +// itself (e.g. /next lastSeenAt handling); without exact matching, a new Pi client joins an +// old buggy daemon and the fix never lands. +function daemonVersionCompatible(daemonVersion: string, clientVersion: string): boolean { + return daemonVersion === clientVersion; } // Ensure the bundled daemon.cjs is copied to a versioned cache dir so each pi-chrome @@ -178,7 +180,7 @@ function waitForDaemonReady(host: string, port: number, timeoutMs = 4_000): Reco while (Date.now() < deadline) { const probed = probeBridgeStatus(host, port); if (probed && typeof (probed as { bridgeVersion?: string }).bridgeVersion === "string" - && sameMajorMinor((probed as { bridgeVersion: string }).bridgeVersion, PI_CHROME_VERSION)) { + && daemonVersionCompatible((probed as { bridgeVersion: string }).bridgeVersion, PI_CHROME_VERSION)) { return probed; } spawnSync("sleep", ["0.1"]); @@ -844,7 +846,7 @@ class ChromeProfileBridge { const ownerVersion = typeof (probed as { bridgeVersion?: string })?.bridgeVersion === "string" ? (probed as { bridgeVersion: string }).bridgeVersion : undefined; - const compatible = ownerVersion ? sameMajorMinor(ownerVersion, PI_CHROME_VERSION) : false; + const compatible = ownerVersion ? daemonVersionCompatible(ownerVersion, PI_CHROME_VERSION) : false; if (probed && compatible) { this.mode = "client"; return; @@ -868,7 +870,7 @@ class ChromeProfileBridge { private async handleEaddrinuse(): Promise<void> { const probed = probeBridgeStatus(this.host, this.port); const ownerVersion = typeof probed?.bridgeVersion === "string" ? probed.bridgeVersion : undefined; - const compatible = ownerVersion ? sameMajorMinor(ownerVersion, PI_CHROME_VERSION) : false; + const compatible = ownerVersion ? daemonVersionCompatible(ownerVersion, PI_CHROME_VERSION) : false; if (probed && compatible) { this.mode = "client"; return; |
