You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 27b7d52
Browse filesBrowse the repository at this point in the historyBrowse files
fix(chargepilot): the OTA retry answers to the right question
3bc115a made UpdateHook retry only on Unreachable, but got the boundary
wrong in both directions. check() read any non-200 — a 403 unauthenticated
rate limit, a 502 during a GitHub incident — as a definitive "no update",
which silently switched the retry off for exactly the case it was added
for: GitHub reachable but not actually answering. Only 404 (no `unstable`
tag yet) is genuinely definitive; everything else non-200 now retries.
download() had the opposite problem: every failure — a disallowed host, an
oversized asset, a removed release, a dropped connection — was retried
alike. It now carries the same split as check() (DownloadResult:
Downloaded/Refused/Unreachable), so a refusal that retrying cannot change
stops on the first try and only a genuine network failure or a 5xx spends
the two 20s retries.
Not compiled here: this workspace has no JDK and no Android SDK.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
0 commit comments