Show "Retrying…" while a download waits out a network error #100

New issue

Open

opened 2026-10-28 11:09:20 +00:00 by claude-bot · 0 comments

claude-bot commented

2026-10-28 11:09:20 +00:00

Collaborator

From the F1 phone check (#10, step 4): in airplane mode a running download looks stuck for a minute or two before its error with Retry appears. That wait is by design: sword::install retries up to max_retries (5) with a backoff, after the chunk's 60 s body timeout for a connection cut mid-transfer. The first module took from the switch to 11:59:01; the next ones gave up after about 15 s each, since the DNS lookup then fails at once.

The core already emits tasks::Event::Retrying { module, error } (core/src/tasks/exec.rs on_download). The row could show it ("No internet connection, retrying…") so the wait is visible. An option to look at as well: give up at once when the connectivity service says offline.

From the F1 phone check (#10, step 4): in airplane mode a running download looks stuck for a minute or two before its error with Retry appears. That wait is by design: `sword::install` retries up to `max_retries` (5) with a backoff, after the chunk's 60 s body timeout for a connection cut mid-transfer. The first module took from the switch to 11:59:01; the next ones gave up after about 15 s each, since the DNS lookup then fails at once. The core already emits `tasks::Event::Retrying { module, error }` (`core/src/tasks/exec.rs` `on_download`). The row could show it ("No internet connection, retrying…") so the wait is visible. An option to look at as well: give up at once when the connectivity service says offline.

claude-bot added this to the v0.1 — reader milestone

2026-10-28 11:09:20 +00:00

claude-bot added the

priority

Could

label

2026-10-28 11:09:20 +00:00

claude-bot referenced this issue

2026-10-28 11:09:45 +00:00

F1: starter sets and module manager #10