I have a few questions below, but they're probably due to lack of a full
understanding on my part of how packfiles are managed.

On 2019.08.26 14:47, Jonathan Tan wrote:
> The specification of promisor packfiles (in partial-clone.txt) states
> that the .promisor files that accompany packfiles do not matter (just
> like .keep files), so whenever a packfile is fetched from the promisor
> remote, Git has been writing empty .promisor files. But these files
> could contain more useful information.
> 
> So instead of writing empty files, write the refs fetched to these
> files. This makes it easier to debug issues with partial clones, as we
> can identify what refs (and their associated hashes) were fetched at the
> time the packfile was downloaded, and if necessary, compare those hashes
> against what the promisor remote reports now.
> 
> Signed-off-by: Jonathan Tan <jonathanta...@google.com>
> ---
> As written in the NEEDSWORK comment, repack does not preserve the
> contents of .promisor files, but I thought I'd send this out anyway as
> this change is already useful for users who don't run repack much.
> ---
>  builtin/repack.c         |  5 +++++
>  fetch-pack.c             | 41 ++++++++++++++++++++++++++++++++++++----
>  t/t5616-partial-clone.sh |  8 ++++++++
>  3 files changed, 50 insertions(+), 4 deletions(-)
> 
> diff --git a/builtin/repack.c b/builtin/repack.c
> index 632c0c0a79..8c1621d414 100644
> --- a/builtin/repack.c
> +++ b/builtin/repack.c
> @@ -232,6 +232,11 @@ static void repack_promisor_objects(const struct 
> pack_objects_args *args,
>               /*
>                * pack-objects creates the .pack and .idx files, but not the
>                * .promisor file. Create the .promisor file, which is empty.
> +              *
> +              * NEEDSWORK: fetch-pack generates non-empty .promisor files,
> +              * but this would not preserve their contents. Maybe
> +              * concatenate the contents of all .promisor files instead of
> +              * just creating a new empty file.
>                */
>               promisor_name = mkpathdup("%s-%s.promisor", packtmp,
>                                         line.buf);

Since this is just diagnostic information, it seems fine. Maybe
explicitly note in the comment what information is being lost?

> diff --git a/fetch-pack.c b/fetch-pack.c
> index 65be043f2a..07029e1bbf 100644
> --- a/fetch-pack.c
> +++ b/fetch-pack.c
> @@ -758,8 +758,33 @@ static int sideband_demux(int in, int out, void *data)
>       return ret;
>  }
>  
> +static void write_promisor_file(const char *keep_name,
> +                             struct ref **sought, int nr_sought)
> +{
> +     struct strbuf promisor_name = STRBUF_INIT;
> +     int suffix_stripped;
> +     FILE *output;
> +     int i;
> +
> +     strbuf_addstr(&promisor_name, keep_name);
> +     suffix_stripped = strbuf_strip_suffix(&promisor_name, ".keep");
> +     if (!suffix_stripped)
> +             BUG("name of pack lockfile should end with .keep (was '%s')",
> +                 keep_name);
> +     strbuf_addstr(&promisor_name, ".promisor");
> +
> +     output = xfopen(promisor_name.buf, "w");
> +     for (i = 0; i < nr_sought; i++)
> +             fprintf(output, "%s %s\n", oid_to_hex(&sought[i]->old_oid),
> +                     sought[i]->name);
> +     fclose(output);
> +
> +     strbuf_release(&promisor_name);
> +}
> +

I am not sure why we want to tie creating the .promisor to creating the
lockfile. I'll keep reading and see if it becomes clear later. Other
than that, the logic here seems clear.

>  static int get_pack(struct fetch_pack_args *args,
> -                 int xd[2], char **pack_lockfile)
> +                 int xd[2], char **pack_lockfile,
> +                 struct ref **sought, int nr_sought)
>  {
>       struct async demux;
>       int do_keep = args->keep_pack;
> @@ -821,7 +846,13 @@ static int get_pack(struct fetch_pack_args *args,
>               }
>               if (args->check_self_contained_and_connected)
>                       argv_array_push(&cmd.args, 
> "--check-self-contained-and-connected");
> -             if (args->from_promisor)
> +             /*
> +              * If we're obtaining the filename of a lockfile, we'll use
> +              * that filename to write a .promisor file with more
> +              * information below. If not, we need index-pack to do it for
> +              * us.
> +              */
> +             if (!(do_keep && pack_lockfile) && args->from_promisor)
>                       argv_array_push(&cmd.args, "--promisor");
>       }
>       else {

This makes me wonder why we don't also change index-pack to write a
similar message to the .promisor. I guess there's potentially too much
information to shove all the refs on the command-line?

> @@ -859,6 +890,8 @@ static int get_pack(struct fetch_pack_args *args,
>               die(_("fetch-pack: unable to fork off %s"), cmd_name);
>       if (do_keep && pack_lockfile) {
>               *pack_lockfile = index_pack_lockfile(cmd.out);
> +             if (args->from_promisor)
> +                     write_promisor_file(*pack_lockfile, sought, nr_sought);
>               close(cmd.out);
>       }
>  

Apart from using the lockfile name as the base for the .promisor
filename, I'm still not seeing why we need to tie this to the fact that
we're creating a lockfile. Could we instead just unconditionally create
the .promisor when args->from_promisor is set, and then remove the logic
in the previous chunk that adds the "--promisor" flag to the index-pack
call?

> @@ -1009,7 +1042,7 @@ static struct ref *do_fetch_pack(struct fetch_pack_args 
> *args,
>               alternate_shallow_file = setup_temporary_shallow(si->shallow);
>       else
>               alternate_shallow_file = NULL;
> -     if (get_pack(args, fd, pack_lockfile))
> +     if (get_pack(args, fd, pack_lockfile, sought, nr_sought))
>               die(_("git fetch-pack: fetch failed."));
>  
>   all_done:
> @@ -1458,7 +1491,7 @@ static struct ref *do_fetch_pack_v2(struct 
> fetch_pack_args *args,
>  
>                       /* get the pack */
>                       process_section_header(&reader, "packfile", 0);
> -                     if (get_pack(args, fd, pack_lockfile))
> +                     if (get_pack(args, fd, pack_lockfile, sought, 
> nr_sought))
>                               die(_("git fetch-pack: fetch failed."));
>  
>                       state = FETCH_DONE;
> diff --git a/t/t5616-partial-clone.sh b/t/t5616-partial-clone.sh
> index 565254558f..486db27ee0 100755
> --- a/t/t5616-partial-clone.sh
> +++ b/t/t5616-partial-clone.sh
> @@ -46,6 +46,14 @@ test_expect_success 'do partial clone 1' '
>       test "$(git -C pc1 config --local core.partialclonefilter)" = 
> "blob:none"
>  '
>  
> +test_expect_success 'verify that .promisor file contains refs fetched' '
> +     ls pc1/.git/objects/pack/pack-*.promisor >promisorlist &&
> +     test_line_count = 1 promisorlist &&
> +     git -C srv.bare rev-list HEAD >headhash &&
> +     grep "$(cat headhash) HEAD" $(cat promisorlist) &&
> +     grep "$(cat headhash) refs/heads/master" $(cat promisorlist)
> +'
> +
>  # checkout master to force dynamic object fetch of blobs at HEAD.
>  test_expect_success 'verify checkout with dynamic object fetch' '
>       git -C pc1 rev-list --quiet --objects --missing=print HEAD >observed &&
> -- 
> 2.23.0.187.g17f5b7556c-goog
> 

Reply via email to