# [PATCH] blame: report correct number of lines in progress when using ranges 6 messages from 2022-04-03 to 2022-04-04. Participants: Edmundo Carmona Antoranz, Junio C Hamano, Ævar Arnfjörð Bjarmason. Thread: https://gitlist.dev/t/57653 ## Edmundo Carmona Antoranz, 2022-04-03 16:50 Subject: [PATCH] blame: report correct number of lines in progress when using ranges Message-ID: <20220403165038.52803-1-eantoranz@gmail.com> URL: https://gitlist.dev/e/20220403165038.52803-1-eantoranz%40gmail.com ``` When using ranges, use their sizes as the limit for progress instead of the size of the full file. Before: $ git blame --progress builtin/blame.c > /dev/null Blaming lines: 100% (1210/1210), done. $ git blame --progress -L 100,120 -L 200,300 builtin/blame.c > /dev/null Blaming lines: 10% (122/1210), done. $ After: $ ./git blame --progress builtin/blame.c > /dev/null Blaming lines: 100% (1210/1210), done. $ ./git blame --progress -L 100,120 -L 200,300 builtin/blame.c > /dev/null Blaming lines: 100% (122/122), done. $ Signed-off-by: Edmundo Carmona Antoranz --- builtin/blame.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/builtin/blame.c b/builtin/blame.c index 8d15b68afc..e33372c56b 100644 --- a/builtin/blame.c +++ b/builtin/blame.c @@ -898,6 +898,7 @@ int cmd_blame(int argc, const char **argv, const char *prefix) unsigned int range_i; long anchor; const int hexsz = the_hash_algo->hexsz; + long num_lines = 0; setup_default_color_by_age(); git_config(git_blame_config, &output_option); @@ -1129,7 +1130,10 @@ int cmd_blame(int argc, const char **argv, const char *prefix) for (range_i = ranges.nr; range_i > 0; --range_i) { const struct range *r = &ranges.ranges[range_i - 1]; ent = blame_entry_prepend(ent, r->start, r->end, o); + num_lines += (r->end - r->start); } + if (!num_lines) + num_lines = sb.num_lines; o->suspects = ent; prio_queue_put(&sb.commits, o->commit); @@ -1158,7 +1162,7 @@ int cmd_blame(int argc, const char **argv, const char *prefix) sb.found_guilty_entry = &found_guilty_entry; sb.found_guilty_entry_data = π if (show_progress) - pi.progress = start_delayed_progress(_("Blaming lines"), sb.num_lines); + pi.progress = start_delayed_progress(_("Blaming lines"), num_lines); assign_blame(&sb, opt); -- 2.35.1 ``` ## Junio C Hamano, 2022-04-03 22:42 Subject: Re: [PATCH] blame: report correct number of lines in progress when using ranges Message-ID: URL: https://gitlist.dev/e/xmqq5ynpu6uv.fsf%40gitster.g In-Reply-To: <20220403165038.52803-1-eantoranz@gmail.com> ``` Edmundo Carmona Antoranz writes: > When using ranges, use their sizes as the limit for progress > instead of the size of the full file. > > Before: > $ git blame --progress builtin/blame.c > /dev/null > Blaming lines: 100% (1210/1210), done. > $ git blame --progress -L 100,120 -L 200,300 builtin/blame.c > /dev/null > Blaming lines: 10% (122/1210), done. > $ > > After: > $ ./git blame --progress builtin/blame.c > /dev/null > Blaming lines: 100% (1210/1210), done. > $ ./git blame --progress -L 100,120 -L 200,300 builtin/blame.c > /dev/null > Blaming lines: 100% (122/122), done. > $ > > Signed-off-by: Edmundo Carmona Antoranz > --- > builtin/blame.c | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) Wow. I am reasonably sure that this was broken since the introduction of the progress meter to "git blame". Thanks for finding and fixing. Can we have a test, too, or is that too cumbersome to add for some reason? Thanks. > diff --git a/builtin/blame.c b/builtin/blame.c > index 8d15b68afc..e33372c56b 100644 > --- a/builtin/blame.c > +++ b/builtin/blame.c > @@ -898,6 +898,7 @@ int cmd_blame(int argc, const char **argv, const char *prefix) > unsigned int range_i; > long anchor; > const int hexsz = the_hash_algo->hexsz; > + long num_lines = 0; > > setup_default_color_by_age(); > git_config(git_blame_config, &output_option); > @@ -1129,7 +1130,10 @@ int cmd_blame(int argc, const char **argv, const char *prefix) > for (range_i = ranges.nr; range_i > 0; --range_i) { > const struct range *r = &ranges.ranges[range_i - 1]; > ent = blame_entry_prepend(ent, r->start, r->end, o); > + num_lines += (r->end - r->start); > } > + if (!num_lines) > + num_lines = sb.num_lines; > > o->suspects = ent; > prio_queue_put(&sb.commits, o->commit); > @@ -1158,7 +1162,7 @@ int cmd_blame(int argc, const char **argv, const char *prefix) > sb.found_guilty_entry = &found_guilty_entry; > sb.found_guilty_entry_data = π > if (show_progress) > - pi.progress = start_delayed_progress(_("Blaming lines"), sb.num_lines); > + pi.progress = start_delayed_progress(_("Blaming lines"), num_lines); > > assign_blame(&sb, opt); ``` ## Edmundo Carmona Antoranz, 2022-04-04 05:27 Subject: Re: [PATCH] blame: report correct number of lines in progress when using ranges Message-ID: URL: https://gitlist.dev/e/CAOc6etac3tQdOzY1bF7qBVOJ_ndns-KOSum8w-Jie06Ynz_cWw%40mail.gmail.com In-Reply-To: ``` On Mon, Apr 4, 2022 at 12:42 AM Junio C Hamano wrote: > > Wow. I am reasonably sure that this was broken since the > introduction of the progress meter to "git blame". Thanks for > finding and fixing. As the person who originally wrote said support, I feel like I am just nurturing it. :-D > > Can we have a test, too, or is that too cumbersome to add for some > reason? Correct me if I'm wrong but it could be a little tricky because "progress display" shows up only if it happens to "lose" a race. Progress is skipped altogether if blame process goes too fast. Even if you run blame on a file with a lot of history, if box is fast enough and info is cached, it will fail to display progress. So, all in all, it would be like trying to unit test output coming out of a race condition. Let me know what you think. > > Thanks. yw ``` ## Ævar Arnfjörð Bjarmason, 2022-04-04 06:12 Subject: Re: [PATCH] blame: report correct number of lines in progress when using ranges Message-ID: <220404.8635itl6h0.gmgdl@evledraar.gmail.com> URL: https://gitlist.dev/e/220404.8635itl6h0.gmgdl%40evledraar.gmail.com In-Reply-To: <20220403165038.52803-1-eantoranz@gmail.com> ``` On Sun, Apr 03 2022, Edmundo Carmona Antoranz wrote: > When using ranges, use their sizes as the limit for progress > instead of the size of the full file. > > Before: > $ git blame --progress builtin/blame.c > /dev/null > Blaming lines: 100% (1210/1210), done. > $ git blame --progress -L 100,120 -L 200,300 builtin/blame.c > /dev/null > Blaming lines: 10% (122/1210), done. > $ > > After: > $ ./git blame --progress builtin/blame.c > /dev/null > Blaming lines: 100% (1210/1210), done. > $ ./git blame --progress -L 100,120 -L 200,300 builtin/blame.c > /dev/null > Blaming lines: 100% (122/122), done. > $ > > Signed-off-by: Edmundo Carmona Antoranz > --- > builtin/blame.c | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/builtin/blame.c b/builtin/blame.c > index 8d15b68afc..e33372c56b 100644 > --- a/builtin/blame.c > +++ b/builtin/blame.c > @@ -898,6 +898,7 @@ int cmd_blame(int argc, const char **argv, const char *prefix) > unsigned int range_i; > long anchor; > const int hexsz = the_hash_algo->hexsz; > + long num_lines = 0; Here ranges's nr is unsigned int, and the "num_lines" is an int, and the argument to start_delayed_progress() is uint64_t, but both of "start" and "end" are "long". But we appand multiple differences to num_lines, are we sure we won't overflow here? > > setup_default_color_by_age(); > git_config(git_blame_config, &output_option); > @@ -1129,7 +1130,10 @@ int cmd_blame(int argc, const char **argv, const char *prefix) > for (range_i = ranges.nr; range_i > 0; --range_i) { > const struct range *r = &ranges.ranges[range_i - 1]; > ent = blame_entry_prepend(ent, r->start, r->end, o); > + num_lines += (r->end - r->start); > } > + if (!num_lines) > + num_lines = sb.num_lines; > > o->suspects = ent; > prio_queue_put(&sb.commits, o->commit); > @@ -1158,7 +1162,7 @@ int cmd_blame(int argc, const char **argv, const char *prefix) > sb.found_guilty_entry = &found_guilty_entry; > sb.found_guilty_entry_data = π > if (show_progress) > - pi.progress = start_delayed_progress(_("Blaming lines"), sb.num_lines); > + pi.progress = start_delayed_progress(_("Blaming lines"), num_lines); > > assign_blame(&sb, opt); ``` ## Ævar Arnfjörð Bjarmason, 2022-04-04 06:15 Subject: Re: [PATCH] blame: report correct number of lines in progress when using ranges Message-ID: <220404.86y20ljrui.gmgdl@evledraar.gmail.com> URL: https://gitlist.dev/e/220404.86y20ljrui.gmgdl%40evledraar.gmail.com In-Reply-To: ``` On Mon, Apr 04 2022, Edmundo Carmona Antoranz wrote: > On Mon, Apr 4, 2022 at 12:42 AM Junio C Hamano wrote: >> >> Wow. I am reasonably sure that this was broken since the >> introduction of the progress meter to "git blame". Thanks for >> finding and fixing. > > As the person who originally wrote said support, I feel like I > am just nurturing it. :-D > >> >> Can we have a test, too, or is that too cumbersome to add for some >> reason? > > Correct me if I'm wrong but it could be a little tricky because "progress > display" shows up only if it happens to "lose" a race. Progress is > skipped altogether if blame process goes too fast. Even if you run > blame on a file with a lot of history, if box is fast enough and info is > cached, it will fail to display progress. So, all in all, it would be like > trying to unit test output coming out of a race condition. > > Let me know what you think. You can make it always show up by using GIT_PROGRESS_DELAY=0, grep for it in existing tests, skimming the code that coupled with --progress should guarantee that it shows up. ``` ## Junio C Hamano, 2022-04-04 16:34 Subject: Re: [PATCH] blame: report correct number of lines in progress when using ranges Message-ID: URL: https://gitlist.dev/e/xmqq5ynost82.fsf%40gitster.g In-Reply-To: <220404.8635itl6h0.gmgdl@evledraar.gmail.com> ``` Ævar Arnfjörð Bjarmason writes: >> diff --git a/builtin/blame.c b/builtin/blame.c >> index 8d15b68afc..e33372c56b 100644 >> --- a/builtin/blame.c >> +++ b/builtin/blame.c >> @@ -898,6 +898,7 @@ int cmd_blame(int argc, const char **argv, const char *prefix) >> unsigned int range_i; >> long anchor; >> const int hexsz = the_hash_algo->hexsz; >> + long num_lines = 0; > > Here ranges's nr is unsigned int, and the "num_lines" is an int, and the > argument to start_delayed_progress() is uint64_t, but both of "start" > and "end" are "long". I see num_lines is a long, which I am guessing was made to match what start and end are, which in turn is to use parse_range_arg(). > But we appand multiple differences to num_lines, are we sure we won't > overflow here? Looking at members of blame_entry and blame_scoreboard structures, I think we make liberal use of "int" in the blame codepath without worrying about those with 16-bit int, or those with files longer than 2G lines, and progress meter showing incorrect values to them is probably the least of our worries ;-) ```