git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v4 2/7] fetch-pack: add refetch

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Mar 31, 2022, 15:09 UTC
Message-ID
<220331.86o81mp2w1.gmgdl@evledraar.gmail.com>
In-Reply-To
<03f0de3d28c00cbfda73f31a21e0fa8f8fe51742.1648476132.git.gitgitgadget@gmail.com>
On Mon, Mar 28 2022, Robert Coup via GitGitGadget wrote:
Show 9 quoted lines
> From: Robert Coup <robert@coup.net.nz>
>
> Allow a "refetch" where the contents of the local object store are
> ignored and a full fetch is performed, not attempting to find or
> negotiate common commits with the remote.
>
> A key use case is to apply a new partial clone blob/tree filter and
> refetch all the associated matching content, which would otherwise not
> be transferred when the commit objects are already present locally.

FWIW it's not clear to me re earlier comments on earlier iterations whether the "noop fetch" is per-se wanted for this feature for some reason, or if it's just much easier to implement than doing what I suggested in: https://lore.kernel.org/git/220228.86ee3m39jf.gmgdl@evledraar.gmail.com/

I don't think such a thing should hold this series up, but as it would be a bit kinder to servers I think it's worth at least noting in the commit message what's desired per-se here, v.s. what's just needed for the convenience of implementation.

I.e. when this series was in an earlier iteration the scope was to repair repository corruption, which I pointed out to you it really couldn't do without more wider changes to the object store management, and at that point having it be NOOP definitely makes sense. The object lookups etc. take shortcuts that "fsck" wouldn't do, so we could be negotiating on the basis of corrupt content.

But now that it's a "fetch what's missing" wouldn't it make more sense to descend from our otherwise-negotiated tips, and find the OIDs that are "complete", if any, and negotiate with those?

Which again, I think it's fine to say "yeah, that would be ideal, but this is easier". I'm just checking if I'm missing some subtlety here...

Show 42 quoted lines
> Signed-off-by: Robert Coup <robert@coup.net.nz>
> ---
>  fetch-pack.c | 46 +++++++++++++++++++++++++++++-----------------
>  fetch-pack.h |  1 +
>  2 files changed, 30 insertions(+), 17 deletions(-)
>
> diff --git a/fetch-pack.c b/fetch-pack.c
> index 87657907e78..4e1e88eea09 100644
> --- a/fetch-pack.c
> +++ b/fetch-pack.c
> @@ -312,19 +312,21 @@ static int find_common(struct fetch_negotiator *negotiator,
>  		const char *remote_hex;
>  		struct object *o;
>  
> -		/*
> -		 * If that object is complete (i.e. it is an ancestor of a
> -		 * local ref), we tell them we have it but do not have to
> -		 * tell them about its ancestors, which they already know
> -		 * about.
> -		 *
> -		 * We use lookup_object here because we are only
> -		 * interested in the case we *know* the object is
> -		 * reachable and we have already scanned it.
> -		 */
> -		if (((o = lookup_object(the_repository, remote)) != NULL) &&
> -				(o->flags & COMPLETE)) {
> -			continue;
> +		if (!args->refetch) {
> +			/*
> +			* If that object is complete (i.e. it is an ancestor of a
> +			* local ref), we tell them we have it but do not have to
> +			* tell them about its ancestors, which they already know
> +			* about.
> +			*
> +			* We use lookup_object here because we are only
> +			* interested in the case we *know* the object is
> +			* reachable and we have already scanned it.
> +			*/
> +			if (((o = lookup_object(the_repository, remote)) != NULL) &&
> +					(o->flags & COMPLETE)) {
> +				continue;
> +			}

nit: remove the {} here nit: this double-indented if can just be one if-statement nit: don't compare against NULL, use ! instead.

Show 11 quoted lines
>  		}
>  
>  		remote_hex = oid_to_hex(remote);
> @@ -692,6 +694,9 @@ static void mark_complete_and_common_ref(struct fetch_negotiator *negotiator,
>  	int old_save_commit_buffer = save_commit_buffer;
>  	timestamp_t cutoff = 0;
>  
> +	if (args->refetch)
> +		return;
> +
>  	save_commit_buffer = 0;

nit: This function has only two callers, perhaps it's clearer to do do this "early abort" in those calls?

Show 11 quoted lines
>  	trace2_region_enter("fetch-pack", "parse_remote_refs_and_find_cutoff", NULL);
> @@ -1028,7 +1033,11 @@ static struct ref *do_fetch_pack(struct fetch_pack_args *args,
>  	struct fetch_negotiator *negotiator;
>  
>  	negotiator = &negotiator_alloc;
> -	fetch_negotiator_init(r, negotiator);
> +	if (args->refetch) {
> +		fetch_negotiator_init_noop(negotiator);
> +	} else {
> +		fetch_negotiator_init(r, negotiator);
> +	}
More needless {}
Show 11 quoted lines
>  	sort_ref_list(&ref, ref_compare_name);
>  	QSORT(sought, nr_sought, cmp_ref_by_name);
> @@ -1121,7 +1130,7 @@ static struct ref *do_fetch_pack(struct fetch_pack_args *args,
>  
>  	mark_complete_and_common_ref(negotiator, args, &ref);
>  	filter_refs(args, &ref, sought, nr_sought);
> -	if (everything_local(args, &ref)) {
> +	if (!args->refetch && everything_local(args, &ref)) {
>  		packet_flush(fd[1]);
>  		goto all_done;
>  	}

Here everything_local() is doing what I suggested for mark_complete_and_common_ref() above, i.e. we check args->refetch first.

Show 9 quoted lines
> @@ -1587,7 +1596,10 @@ static struct ref *do_fetch_pack_v2(struct fetch_pack_args *args,
>  	struct strvec index_pack_args = STRVEC_INIT;
>  
>  	negotiator = &negotiator_alloc;
> -	fetch_negotiator_init(r, negotiator);
> +	if (args->refetch)
> +		fetch_negotiator_init_noop(negotiator);
> +	else
> +		fetch_negotiator_init(r, negotiator);
This one doesn't have braces (good), unlike do_fetch_pack()
Previous: Robert Coup via GitGitGadgetNext: Robert Coup
Message 63 of 76 in “[RFC] partial-clone: add ability to refetch with expanded filter”
  1. 0/6 [RFC] partial-clone: add ability to refetch with expanded filterRobert Coup via GitGitGadget, Feb 1, 2022
  2. 1/6 fetch-negotiator: add specific noop initializorRobert Coup via GitGitGadget, Feb 1, 2022
  3. 2/6 fetch-pack: add partial clone refilteringRobert Coup via GitGitGadget, Feb 1, 2022
  4. Jonathan TanFeb 4, 2022
  5. Robert CoupFeb 11, 2022
  6. Jonathan TanFeb 17, 2022
  7. 3/6 builtin/fetch-pack: add --refilter optionRobert Coup via GitGitGadget, Feb 1, 2022
  8. 4/6 fetch: add --refilter optionRobert Coup via GitGitGadget, Feb 1, 2022
  9. 5/6 t5615-partial-clone: add test for --refilterRobert Coup via GitGitGadget, Feb 1, 2022
  10. 6/6 doc/partial-clone: mention --refilter optionRobert Coup via GitGitGadget, Feb 1, 2022
  11. Junio C HamanoFeb 1, 2022
  12. Robert CoupFeb 2, 2022
  13. Robert CoupFeb 16, 2022
  14. Jonathan TanFeb 2, 2022
  15. Robert CoupFeb 2, 2022
  16. Robert CoupFeb 2, 2022
  17. Jeff HostetlerFeb 7, 2022
  18. 0/8 fetch: add repair: full refetch without negotiation (was: "refiltering")Robert Coup via GitGitGadget, Feb 24, 2022
  19. 8/8 doc/partial-clone: mention --repair fetch optionRobert Coup via GitGitGadget, Feb 24, 2022
  20. 3/8 builtin/fetch-pack: add --repair optionRobert Coup via GitGitGadget, Feb 24, 2022
  21. 2/8 fetch-pack: add repairingRobert Coup via GitGitGadget, Feb 24, 2022
  22. Junio C HamanoFeb 25, 2022
  23. Robert CoupFeb 28, 2022
  24. 1/8 fetch-negotiator: add specific noop initializorRobert Coup via GitGitGadget, Feb 24, 2022
  25. Junio C HamanoFeb 25, 2022
  26. Robert CoupFeb 28, 2022
  27. 4/8 fetch: add --repair optionRobert Coup via GitGitGadget, Feb 24, 2022
  28. 5/8 t5615-partial-clone: add test for fetch --repairRobert Coup via GitGitGadget, Feb 24, 2022
  29. 6/8 maintenance: add ability to pass config optionsRobert Coup via GitGitGadget, Feb 24, 2022
  30. Junio C HamanoFeb 25, 2022
  31. Robert CoupFeb 28, 2022
  32. Junio C HamanoFeb 28, 2022
  33. Ævar Arnfjörð BjarmasonFeb 25, 2022
  34. Robert CoupFeb 28, 2022
  35. 7/8 fetch: after repair, encourage auto gc repackingRobert Coup via GitGitGadget, Feb 24, 2022
  36. Ævar Arnfjörð BjarmasonFeb 28, 2022
  37. Ævar Arnfjörð BjarmasonFeb 28, 2022
  38. Robert CoupFeb 28, 2022
  39. Junio C HamanoFeb 28, 2022
  40. Ævar Arnfjörð BjarmasonFeb 28, 2022
  41. 0/7 fetch: add repair: full refetch without negotiation (was: "refiltering")Robert Coup via GitGitGadget, Mar 4, 2022
  42. 1/7 fetch-negotiator: add specific noop initializerRobert Coup via GitGitGadget, Mar 4, 2022
  43. 3/7 builtin/fetch-pack: add --refetch optionRobert Coup via GitGitGadget, Mar 4, 2022
  44. 2/7 fetch-pack: add refetchRobert Coup via GitGitGadget, Mar 4, 2022
  45. 4/7 fetch: add --refetch optionRobert Coup via GitGitGadget, Mar 4, 2022
  46. Junio C HamanoMar 4, 2022
  47. Robert CoupMar 7, 2022
  48. Junio C HamanoMar 7, 2022
  49. Robert CoupMar 9, 2022
  50. 5/7 t5615-partial-clone: add test for fetch --refetchRobert Coup via GitGitGadget, Mar 4, 2022
  51. 6/7 fetch: after refetch, encourage auto gc repackingRobert Coup via GitGitGadget, Mar 4, 2022
  52. 7/7 doc/partial-clone: mention --refetch fetch optionRobert Coup via GitGitGadget, Mar 4, 2022
  53. Calvin WanMar 9, 2022
  54. Robert CoupMar 9, 2022
  55. Junio C HamanoMar 9, 2022
  56. Calvin WanMar 10, 2022
  57. Robert CoupMar 10, 2022
  58. Calvin WanMar 21, 2022
  59. Robert CoupMar 21, 2022
  60. 0/7 fetch: add repair: full refetch without negotiation (was: "refiltering")Robert Coup via GitGitGadget, Mar 28, 2022
  61. 1/7 fetch-negotiator: add specific noop initializerRobert Coup via GitGitGadget, Mar 28, 2022
  62. 2/7 fetch-pack: add refetchRobert Coup via GitGitGadget, Mar 28, 2022
  63. Ævar Arnfjörð BjarmasonMar 31, 2022
  64. Robert CoupApr 1, 2022
  65. 3/7 builtin/fetch-pack: add --refetch optionRobert Coup via GitGitGadget, Mar 28, 2022
  66. 5/7 t5615-partial-clone: add test for fetch --refetchRobert Coup via GitGitGadget, Mar 28, 2022
  67. Ævar Arnfjörð BjarmasonMar 31, 2022
  68. Robert CoupApr 1, 2022
  69. 4/7 fetch: add --refetch optionRobert Coup via GitGitGadget, Mar 28, 2022
  70. Ævar Arnfjörð BjarmasonMar 31, 2022
  71. Robert CoupApr 1, 2022
  72. 6/7 fetch: after refetch, encourage auto gc repackingRobert Coup via GitGitGadget, Mar 28, 2022
  73. Ævar Arnfjörð BjarmasonMar 31, 2022
  74. Robert CoupApr 1, 2022
  75. 7/7 docs: mention --refetch fetch optionRobert Coup via GitGitGadget, Mar 28, 2022
  76. Junio C HamanoMar 28, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.