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

Re: [PATCH v4 6/8] transport: add object-info fallback to fetch

From
JTJonathan Tan <jonathantanmy@google.com>
Date
May 3, 2022, 23:27 UTC
Message-ID
<20220503232701.4173948-1-jonathantanmy@google.com>
In-Reply-To
<20220502170904.2770649-7-calvinwan@google.com>
Calvin Wan <calvinwan@google.com> writes:
> If a v2 server does not support object-info or if the client requests
> information that isn't supported by object-info, fetch the objects as if
> it were a standard v2 fetch (however without changing any refs).

What do you mean by "however without changing any refs"? (I would have expected that no refs would be changed, so this, to me, implies that we would expect some refs to be changed.)

Show 23 quoted lines
> diff --git a/fetch-pack.c b/fetch-pack.c
> index 506ca28e05..938d082b80 100644
> --- a/fetch-pack.c
> +++ b/fetch-pack.c
> @@ -1639,6 +1639,9 @@ static struct ref *do_fetch_pack_v2(struct fetch_pack_args *args,
>  	if (args->depth > 0 || args->deepen_since || args->deepen_not)
>  		args->deepen = 1;
>  
> +	if (args->object_info)
> +		state = FETCH_SEND_REQUEST;
> +
>  	while (state != FETCH_DONE) {
>  		switch (state) {
>  		case FETCH_CHECK_LOCAL:
> @@ -1648,7 +1651,7 @@ static struct ref *do_fetch_pack_v2(struct fetch_pack_args *args,
>  			/* Filter 'ref' by 'sought' and those that aren't local */
>  			mark_complete_and_common_ref(negotiator, args, &ref);
>  			filter_refs(args, &ref, sought, nr_sought);
> -			if (!args->refetch && everything_local(args, &ref))
> +			if (!args->refetch && !args->object_info && everything_local(args, &ref))
>  				state = FETCH_DONE;
>  			else
>  				state = FETCH_SEND_REQUEST;

I think that the purpose of all these changes is to skip certain steps when we know that we're fetching as a fallback for object-info, but I don't think they're necessary - it's fine to not fetch certain objects if we have them present.

Show 13 quoted lines
> @@ -2035,6 +2038,15 @@ struct ref *fetch_pack(struct fetch_pack_args *args,
>  		args->connectivity_checked = 1;
>  	}
>  
> +	if (args->object_info) {
> +		struct ref *ref_cpy_reader = ref_cpy;
> +		int i = 0;
> +		while (ref_cpy_reader) {
> +			oid_object_info_extended(the_repository, &ref_cpy_reader->old_oid, &(*args->object_info_data)[i], OBJECT_INFO_LOOKUP_REPLACE);
> +			ref_cpy_reader = ref_cpy_reader->next;
> +			i++;
> +		}
> +	}

Could this part be done in the same function that falls back (fetch_refs_via_pack(), I believe)? That would make the code easier to understand - here, we don't know why we would need to copy the OIDs, but in the function that falls back, we can look up and see that this is done because we couldn't do something else.

Show 14 quoted lines
> diff --git a/transport.c b/transport.c
> index 08c505e1d0..b85e52d9a8 100644
> --- a/transport.c
> +++ b/transport.c
> @@ -436,10 +436,12 @@ static int fetch_refs_via_pack(struct transport *transport,
>  			       int nr_heads, struct ref **to_fetch)
>  {
>  	int ret = 0;
> +	size_t i;
>  	struct git_transport_data *data = transport->data;
>  	struct ref *refs = NULL;
>  	struct fetch_pack_args args;
>  	struct ref *refs_tmp = NULL;
> +	struct ref *wanted_refs = xcalloc(1, sizeof (struct ref));

If you only need these new variables in a block, declare them there (and free them at the end of that block).

Show 9 quoted lines
> @@ -489,7 +500,7 @@ static int fetch_refs_via_pack(struct transport *transport,
>  	else if (data->version <= protocol_v1)
>  		die_if_server_options(transport);
>  
> -	if (data->options.acked_commits) {
> +	if (data->options.acked_commits && !transport->smart_options->object_info) {
>  		if (data->version < protocol_v2) {
>  			warning(_("--negotiate-only requires protocol v2"));
>  			ret = -1;

Is this addition necessary? --negotiate-only and object-info do not work together.

Previous: Calvin WanNext: Calvin Wan
Message 58 of 103 in “fetch —object-info-format: client option for object-info”
  1. fetch —object-info-format: client option for object-infoCalvin Wan, Feb 8, 2022
  2. fetch —object-info-format: client option for object-infoCalvin Wan, Feb 8, 2022
  3. Philip OakleyFeb 9, 2022
  4. Calvin WanFeb 10, 2022
  5. Jonathan TanFeb 9, 2022
  6. Calvin WanFeb 10, 2022
  7. 0/3 object-info: add option for retrieving object infoCalvin Wan, Mar 28, 2022
  8. 1/3 fetch-pack: refactor packet writing and fetch optionsCalvin Wan, Mar 28, 2022
  9. Junio C HamanoMar 29, 2022
  10. Taylor BlauMar 29, 2022
  11. Jonathan TanMar 30, 2022
  12. 2/3 transfer.advertiseObjectInfo: add object-info configCalvin Wan, Mar 28, 2022
  13. Junio C HamanoMar 29, 2022
  14. Calvin WanMar 29, 2022
  15. Taylor BlauMar 29, 2022
  16. 3/3 object-info: add option for retrieving object infoCalvin Wan, Mar 28, 2022
  17. Junio C HamanoMar 29, 2022
  18. Junio C HamanoMar 29, 2022
  19. Junio C HamanoMar 30, 2022
  20. Calvin WanMar 30, 2022
  21. Jonathan TanMar 30, 2022
  22. Junio C HamanoMar 30, 2022
  23. Taylor BlauMar 29, 2022
  24. Calvin WanMar 30, 2022
  25. John CaiMar 30, 2022
  26. Calvin WanMar 31, 2022
  27. Junio C HamanoApr 1, 2022
  28. Jonathan TanMar 30, 2022
  29. Josh SteadmonMar 30, 2022
  30. Calvin WanMar 30, 2022
  31. Junio C HamanoMar 29, 2022
  32. Calvin WanMar 29, 2022
  33. Junio C HamanoMar 31, 2022
  34. 0/8 cat-file: add --batch-command remote-object-info commandCalvin Wan, May 2, 2022
  35. 1/8 fetch-pack: refactor packet writingCalvin Wan, May 2, 2022
  36. 3/8 object-store: add function to free object_info contentsCalvin Wan, May 2, 2022
  37. Junio C HamanoMay 2, 2022
  38. Junio C HamanoMay 4, 2022
  39. Junio C HamanoMay 5, 2022
  40. Calvin WanMay 5, 2022
  41. Junio C HamanoMay 5, 2022
  42. 4/8 object-info: send attribute packet regardless of object idsCalvin Wan, May 2, 2022
  43. Junio C HamanoMay 3, 2022
  44. Calvin WanMay 3, 2022
  45. Jonathan TanMay 3, 2022
  46. 2/8 fetch-pack: move fetch default settingsCalvin Wan, May 2, 2022
  47. Junio C HamanoMay 2, 2022
  48. Jonathan TanMay 3, 2022
  49. Calvin WanMay 5, 2022
  50. 5/8 transport: add client side capability to request object-infoCalvin Wan, May 2, 2022
  51. Junio C HamanoMay 3, 2022
  52. Calvin WanMay 3, 2022
  53. Junio C HamanoMay 4, 2022
  54. Jonathan TanMay 3, 2022
  55. Junio C HamanoMay 4, 2022
  56. 7/8 cat-file: move parse_cmd and DEFAULT_FORMAT upCalvin Wan, May 2, 2022
  57. 6/8 transport: add object-info fallback to fetchCalvin Wan, May 2, 2022
  58. Jonathan TanMay 3, 2022
  59. 8/8 cat-file: add --batch-command remote-object-info commandCalvin Wan, May 2, 2022
  60. Jonathan TanMay 4, 2022
  61. Calvin WanMay 5, 2022
  62. Junio C HamanoMay 5, 2022
  63. Junio C HamanoMay 5, 2022
  64. Calvin WanMay 5, 2022
  65. ZheNing HuJul 31, 2022
  66. Calvin WanAug 8, 2022
  67. 0/6 cat-file: add --batch-command remote-object-info commandCalvin Wan, Jul 28, 2022
  68. Junio C HamanoJul 28, 2022
  69. Junio C HamanoJul 29, 2022
  70. Phillip WoodJul 31, 2022
  71. Calvin WanAug 4, 2022
  72. Junio C HamanoSep 30, 2022
  73. 1/6 fetch-pack: refactor packet writingCalvin Wan, Jul 28, 2022
  74. 2/6 fetch-pack: move fetch initializationCalvin Wan, Jul 28, 2022
  75. 3/6 protocol-caps: initialization bug fixCalvin Wan, Jul 28, 2022
  76. Junio C HamanoJul 29, 2022
  77. 4/6 serve: advertise object-info featureCalvin Wan, Jul 28, 2022
  78. Junio C HamanoJul 29, 2022
  79. Calvin WanAug 1, 2022
  80. Ævar Arnfjörð BjarmasonAug 1, 2022
  81. Junio C HamanoAug 1, 2022
  82. Calvin WanAug 1, 2022
  83. 5/6 transport: add client support for object-infoCalvin Wan, Jul 28, 2022
  84. Junio C HamanoJul 29, 2022
  85. Calvin WanAug 4, 2022
  86. Phillip WoodAug 1, 2022
  87. Calvin WanAug 4, 2022
  88. Phillip WoodAug 8, 2022
  89. Phillip WoodAug 1, 2022
  90. Phillip WoodAug 8, 2022
  91. 6/6 cat-file: add remote-object-info to batch-commandCalvin Wan, Jul 28, 2022
  92. Ævar Arnfjörð BjarmasonJul 29, 2022
  93. ZheNing HuAug 7, 2022
  94. Calvin WanAug 8, 2022
  95. Ævar Arnfjörð BjarmasonAug 11, 2022
  96. Junio C HamanoJul 29, 2022
  97. Calvin WanAug 8, 2022
  98. Ævar Arnfjörð BjarmasonSep 28, 2022
  99. ZheNing HuJul 31, 2022
  100. Calvin WanAug 8, 2022
  101. Junio C HamanoAug 13, 2022
  102. John CaiFeb 9, 2022
  103. Calvin WanFeb 10, 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.