Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
duniter
duniter
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 191
    • Issues 191
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nodes
  • typescript
  • duniterduniter
  • Issues
  • #969

Closed
Open
Created May 01, 2017 by Cédric Moreau@c-geekOwner

Add a `--slow` option for `sync` command

On very low connections (< 100 Kb/s), the sync will likely fail at some point.

But it could work if the number of download slots was limited to 1. I've tested it, it works.

Also, there is a bug on local storage of downloaded chunks: they are not stored on a brand new installation, so when the download eventually fail, we have to start the whole download again.

Diagnostic: replace localNumber == 0 by localNumber <= 0 in the downloadChunk function.

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