syntaqxRetrying a read that gets no answer never becomes a loop (after 71274eeb): a refresh of the page already showing kept trying every 5 s for as long as it took, which is right while the browser is offline but not on a network that is up and never answers (an extension or proxy blocking g1t's .data requests, a security policy, broken DNS): the page sat on old data under "Can't reach g1t" forever and never showed what was wrong, and a tab out of view kept asking too. Now a refresh counts only the time it waited while the browser said it was online, and gives up after 2 minutes of that (REFRESH_PATIENCE_MS); offline still waits as long as it lasts. Nothing is retried from a tab out of view: a wait that is over holds until the tab is looked at. While the error page tries on its own (lib/reconnect.ts, 3 s, 6 s, 12 s, then every 30 s), reads are tried once each instead of retrying underneath it, so a broken network costs one request every 30 s on a visible error page and none on a hidden one. A real error (an answer that is an error) was already never retried and stops the error page's trying. keepTrying in lib/resilient-fetch.ts makes the call. Checked: apps/web tsc -b; npm test (985; new: offline waited out however long, up-and-silent gives up for a refresh and a click, one try while the error page tries).992effdHistory
- ..
- 0001_init.sql
- 0002_dependencies.sql
- 0003_repo_deleted.sql
- 0004_repo_archived.sql
- 0005_description_inherits.sql
- 0006_workspace_deleted.sql
- 0007_deploys.sql
- 0008_pins.sql
- 0009_activity.sql
- 0010_kind_and_links.sql
- 0011_drop_dependencies.sql
- 0012_production_image.sql
- 0013_reports_production.sql
- 0014_descriptions_are_projects.sql
- 0015_drop_repo_description.sql
- 0016_sweeps.sql