Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #20777

Closed
Open
Created Nov 26, 2016 by Yawning Angel@yawning

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

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking