updater error: net::ERR_INTERNET_DISCONNECTED #15

Activity

1. sentry

   added

   bugSomething isn't workingSomething isn't working

   sentryAuto-created from Sentry crash reportAuto-created from Sentry crash report

   needs-triageAwaiting initial reviewAwaiting initial review

   on Jun 28, 2026
2. codedev-david commented on Jun 28, 2026

   

   codedev-david

   on Jun 28, 2026

   Owner

   More actions

   Auto-triage attempted but tests failed under the candidate fix. Human review needed. Log: C:\Users\DavidEngelhart\AppData\Local\termpolis\auto-triage\run-20260628-010333.log
3. codedev-david

   added

   auto-triage-attemptedAuto-triage script has tried to fix this issueAuto-triage script has tried to fix this issue

   on Jun 28, 2026
4. codedev-david

   added a commit that references this issue on Jun 28, 2026

   fix(updater): treat offline/transient network errors as benign, not S…

   ...

   9af38d2
5. codedev-david commented on Jun 28, 2026

   

   codedev-david

   on Jun 28, 2026

   Owner

   More actions

   Fixed in 9af38d2. net::ERR_INTERNET_DISCONNECTED is a benign offline/transient-network condition during the update check (auto-update just can't reach the server). New isTransientNetworkError() routes these (and other net::ERR_* / Node socket errnos) to a benign not-available state — exactly like the missing-config case (#14) — so they no longer report to Sentry; genuine errors (e.g. sha512 mismatch) still report. Verified by unit tests + the full coverage gate. Ships in the next release (v1.15.13).
6. codedev-david

   closed this as completedon Jun 28, 2026
7. codedev-david

   added a commit that references this issue on Jun 28, 2026

   chore(release): v1.15.13 — ships updater offline-error fix (#15), all…

   ...

   b81fe57
8. codedev-david

   added a commit that references this issue on Oct 17, 2026

   Stop filing a dropped updater connection as a bug (#37)

   ...

   44c614a