lp:~juan-f/duplicity/progress

Branch merges

Propose for merging

No branches dependent on this one.

Merged into lp:duplicity/0.6 at revision 916

duplicity-team: Pending (new feature) requested 2013-01-25

Diff: 850 lines (+580/-10) (has conflicts)

10 files modified

bin/duplicity (+56/-1)
bin/duplicity.1 (+14/-0)
duplicity/backend.py (+1/-0)
duplicity/backends/_boto_multi.py (+46/-3)
duplicity/backends/_boto_single.py (+7/-1)
duplicity/commandline.py (+6/-0)
duplicity/diffdir.py (+6/-5)
duplicity/globals.py (+11/-0)
duplicity/log.py (+79/-0)
duplicity/progress.py (+354/-0)

api

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

922. By Juan A. Moya Vicén on 2013-04-15

progress: Removed an unneeded if

921. By Juan A. Moya Vicén on 2013-04-11

progress: Fixes for the previous commit after extensive testing:
    - Fixed the index computation for the rotating cache of Snapshots
    - Moved the start point for the Log progress thread after a proper
      computation of the starting volume in case of restart, and adapted
      code for it

920. By Juan A. Moya Vicén on 2013-04-11

progress: Cover the sigtar and manifest upload with the progress reporting. Now the last 1% will be dedicated to this upload and properly report stallment when network goes off while this happens.

919. By Juan A. Moya Vicén on 2013-04-10

progress: Fixed a missing condition for when the progress flag is not used

918. By Juan A. Moya Vicén on 2013-04-10

progress: Cap data progress upload from 0..99% and show 100% only when sigtar and manifest file has uploaded correctly

917. By Juan A. Moya Vicén on 2013-04-10

progress: Avoid completed percentage to drops between backup retries when backup fails and has to be restarted.
          The current progress is offset by the previous uncompleted backup from the last volume that upload correctly.
          To achieve it, the progress tracker now snapshots the current progress to the cache each completed volume, then
          recovers this information later when retrying a failed backup.

916. By Juan A. Moya Vicén on 2013-03-26

progress: The algorithm now will drop the confidence interval adaptively when overpassing the 100%. This may happen when the sigma is large due to a very heterogeneous distribution of the size of deltas in files. In this case, the C.I. will be drop by half to adapt to the variability. If it happens again, it will disregard the sigma and trust the mean only.

915. By Juan A. Moya Vicén on 2013-03-21

progress: Simplified computation of progress to compute an upper bound, fit to a smooth curve. This method embraces better more "change distribution" scenarios and is much simpler to compute. And also, full backups will assume 1:1 correspondence in change distribution, so progress bars during full will be computed linearly, which is closer to reality.

914. By Juan A. Moya Vicén on 2013-02-05

progress: Reporting speed in bps for log file

913. By Juan A. Moya Vicén on 2013-02-04

progress: Changed verbosity to NOTICE, so progress messages appears by default when --progress flag is on