Opened 4 years ago

Closed 3 years ago

#20777 closed enhancement (fixed)

Investigate ways to make the install/update download process more robust.

Reported by: yawning Owned by: yawning
Priority: Medium Milestone:
Component: Archived/Tor Browser Sandbox Version:
Severity: Normal Keywords: sandbox-update
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


In particular this applies to updates that are always fetched over tor. The file downloader should be more robust to failures and maybe transparently retry without kicking the user back to the interface.

In the case of failures I'm not sure if I should force a new circuit or not either...

If/when the update process moves to being done primarily in the background, this can pushed back because the background downloader can be made to retry properly with less thought about the UX.

Child Tickets

Change History (5)

comment:1 Changed 4 years ago by yawning

Priority: MediumHigh

Bump up the priority on things I think are important for 0.0.2.

comment:2 Changed 4 years ago by yawning

Keywords: Yawning201612 added
Status: newaccepted

Tagging these as the things I will be focusing on for the rest of the year.

comment:3 Changed 4 years ago by yawning

Keywords: sandbox-update added

comment:4 Changed 4 years ago by yawning

Keywords: Yawning201612 removed
Priority: HighMedium
Status: acceptednew

Punting on this, since the code will probably fall back if downloading the incremental update fails.

comment:5 Changed 3 years ago by yawning

Resolution: fixed
Status: newclosed

Calling this fixed, because the fallback path exists. It's primarily of importantce for updates, and background updates, if/when they happen basically "solve" or at least mask this issue, so there's no point in spending additional effort here.

Note: See TracTickets for help on using tickets.