path: root/progress.c
diff options
authorJeff King <>2017-12-04 22:05:23 (GMT)
committerJunio C Hamano <>2017-12-04 22:22:17 (GMT)
commitee85e41af3f87afedd9fba63617e74713449240c (patch)
tree9e2534a227141cf4244bf9a076d3f1fedcc33b7d /progress.c
parentcb5918aa0d50f50e83787f65c2ddc3dcb10159fe (diff)
progress: set default delay threshold to 100%, not 0%
Commit 8aade107dd (progress: simplify "delayed" progress API, 2017-08-19) dropped the parameter by which callers could say "show my progress only if I haven't passed M% progress after N seconds". The intent was to just show nothing for 2 seconds, and then always progress after that. But we flipped the logic in the wrapper: it sets M=0, meaning that we'd almost _never_ show progress after 2 seconds, since we'd generally have made some progress. This should have been 100%, not 0%. We were fooled by existing calls like: start_progress_delay("foo", 0, 0, 2); which behaved this way. The trick is that the first "0" there is "how many items total", and there zero means "we don't know". And without knowing that, we cannot compute a completed percent at all, and we ignored the threshold parameter entirely! Modeling our wrapper after that broke callers which pass a non-zero value for "total". We can switch to the intended behavior by using "100" in the wrapper call. Reported-by: Lars Schneider <> Signed-off-by: Jeff King <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'progress.c')
1 files changed, 1 insertions, 1 deletions
diff --git a/progress.c b/progress.c
index 289678d..b774cb1 100644
--- a/progress.c
+++ b/progress.c
@@ -229,7 +229,7 @@ static struct progress *start_progress_delay(const char *title, unsigned total,
struct progress *start_delayed_progress(const char *title, unsigned total)
- return start_progress_delay(title, total, 0, 2);
+ return start_progress_delay(title, total, 100, 2);
struct progress *start_progress(const char *title, unsigned total)