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

Re: [PATCH v4 12/12] sequencer: notify user of --update-refs activity

From
PWPhillip Wood <phillip.wood123@gmail.com>
Date
Jul 15, 2022, 10:12 UTC
Message-ID
<11ff21b9-7169-00c5-95c0-130675ffe2ae@gmail.com>
In-Reply-To
<d5cd4b49e46bc2c186c6e89333360a975700c99a.1657631226.git.gitgitgadget@gmail.com>
On 12/07/2022 14:07, Derrick Stolee via GitGitGadget wrote:
Show 20 quoted lines
> From: Derrick Stolee <derrickstolee@github.com>
> 
> When the user runs 'git rebase -i --update-refs', the end message still
> says only
> 
>    Successfully rebased and updated <HEAD-ref>.
> 
> Update the sequencer to collect the successful (and unsuccessful) ref
> updates due to the --update-refs option, so the end message now says
> 
>    Successfully rebased and updated <HEAD-ref>.
>    Updated the following refs with --update-refs:
> 	refs/heads/first
> 	refs/heads/third
>    Failed to update the following refs with --update-refs:
> 	refs/heads/second
> 
> To test this output, we need to be very careful to format the expected
> error to drop the leading tab characters. Also, we need to be aware that
> the verbose output from 'git rebase' is writing progress lines which
s/is writing/writes/ ?
> don't use traditional newlines but clear the line after every progress
> item is complete.

I was a bit confused by the reference to "verbose output" in this paragraph. When the user passes --verbose then we do actually use NL, it is when the user does not pass verbose that we use CR instead.

Show 5 quoted lines
> When opening the error file in an editor, these lines
> are visible, but when looking at the diff in a terminal those lines
> disappear because of the characters that delete the previous characters.
> Use 'sed' to clear those progress lines and clear the tabs so we can get
> an exact match on our expected output.

Thanks for the comprehensive commit message and for implementing an excellent suggestion from Elijah. I wonder if it makes sense to distinguish between the current branch and all the others when writing the update message as we do here or if all the refs should just be in a single list. I also think it doesn't matter much and we can change it later if we want.

 From the last test it looks like we are already printing something when 
we fail to update a ref (possibly this comes from the refs backend code) 
I don't think it hurts to print a summary of them all after that though.
Show 57 quoted lines
> Reported-by: Elijah Newren <newren@gmail.com>
> Signed-off-by: Derrick Stolee <derrickstolee@github.com>
> ---
>   sequencer.c                   | 40 +++++++++++++++++++++++++++++------
>   t/t3404-rebase-interactive.sh | 35 +++++++++++++++++++++++++++---
>   2 files changed, 66 insertions(+), 9 deletions(-)
> 
> diff --git a/sequencer.c b/sequencer.c
> index 82ef062d497..bdc67c66f3e 100644
> --- a/sequencer.c
> +++ b/sequencer.c
> @@ -4257,17 +4257,20 @@ static int do_update_ref(struct repository *r, const char *refname)
>   	return 0;
>   }
>   
> -static int do_update_refs(struct repository *r)
> +static int do_update_refs(struct repository *r, int quiet)
>   {
>   	int res = 0;
>   	struct string_list_item *item;
>   	struct string_list refs_to_oids = STRING_LIST_INIT_DUP;
>   	struct ref_store *refs = get_main_ref_store(r);
> +	struct strbuf update_msg = STRBUF_INIT;
> +	struct strbuf error_msg = STRBUF_INIT;
>   
>   	sequencer_get_update_refs_state(r->gitdir, &refs_to_oids);
>   
>   	for_each_string_list_item(item, &refs_to_oids) {
>   		struct update_ref_record *rec = item->util;
> +		int loop_res;
>   
>   		if (oideq(&rec->after, the_hash_algo->null_oid)) {
>   			/*
> @@ -4277,13 +4280,38 @@ static int do_update_refs(struct repository *r)
>   			continue;
>   		}
>   
> -		res |= refs_update_ref(refs, "rewritten during rebase",
> -				       item->string,
> -				       &rec->after, &rec->before,
> -				       0, UPDATE_REFS_MSG_ON_ERR);
> +		loop_res = refs_update_ref(refs, "rewritten during rebase",
> +					   item->string,
> +					   &rec->after, &rec->before,
> +					   0, UPDATE_REFS_MSG_ON_ERR);
> +		res |= loop_res;
> +
> +		if (quiet)
> +			continue;
> +
> +		if (loop_res)
> +			strbuf_addf(&error_msg, "\t%s\n", item->string);
> +		else
> +			strbuf_addf(&update_msg, "\t%s\n", item->string);
> +	}
> +
> +	if (!quiet &&

As you skip adding anything to the strbufs when quiet is true you don't really need this test

Show 5 quoted lines
> +	    (update_msg.len || error_msg.len)) {
> +		fprintf(stderr,
> +			_("Updated the following refs with %s:\n%s"),
> +			"--update-refs",
> +			update_msg.buf);
This will be printed even if all the updates falied
Show 74 quoted lines
> +
> +		if (res)
> +			fprintf(stderr,
> +				_("Failed to update the following refs with %s:\n%s"),
> +				"--update-refs",
> +				error_msg.buf);
>   	}
>   
>   	string_list_clear(&refs_to_oids, 1);
> +	strbuf_release(&update_msg);
> +	strbuf_release(&error_msg);
>   	return res;
>   }
>   
> @@ -4804,7 +4832,7 @@ cleanup_head_ref:
>   		strbuf_release(&head_ref);
>   	}
>   
> -	do_update_refs(r);
> +	do_update_refs(r, opts->quiet);
>   
>   	/*
>   	 * Sequence of picks finished successfully; cleanup by
> diff --git a/t/t3404-rebase-interactive.sh b/t/t3404-rebase-interactive.sh
> index 4b7b77a4123..ef902b5431f 100755
> --- a/t/t3404-rebase-interactive.sh
> +++ b/t/t3404-rebase-interactive.sh
> @@ -1836,12 +1836,26 @@ test_expect_success '--update-refs updates refs correctly' '
>   	test_commit extra2 fileX &&
>   	git commit --amend --fixup=L &&
>   
> -	git rebase -i --autosquash --update-refs primary &&
> +	git rebase -i --autosquash --update-refs primary 2>err &&
>   
>   	test_cmp_rev HEAD~3 refs/heads/first &&
>   	test_cmp_rev HEAD~3 refs/heads/second &&
>   	test_cmp_rev HEAD~1 refs/heads/third &&
> -	test_cmp_rev HEAD refs/heads/no-conflict-branch
> +	test_cmp_rev HEAD refs/heads/no-conflict-branch &&
> +
> +	cat >expect <<-\EOF &&
> +	Successfully rebased and updated refs/heads/update-refs.
> +	Updated the following refs with --update-refs:
> +		refs/heads/first
> +		refs/heads/no-conflict-branch
> +		refs/heads/second
> +		refs/heads/third
> +	EOF
> +
> +	# Clear "Rebasing (X/Y)" progress lines and drop leading tabs.
> +	sed -e "s/Rebasing.*Successfully/Successfully/g" -e "s/^\t//g" \
> +		<err >err.trimmed &&
> +	test_cmp expect err.trimmed
>   '
>   
>   test_expect_success 'respect user edits to update-ref steps' '
> @@ -1980,7 +1994,22 @@ test_expect_success '--update-refs: check failed ref update' '
>   	git rev-parse third >.git/refs/heads/second &&
>   
>   	git rebase --continue 2>err &&
> -	grep "update_ref failed for ref '\''refs/heads/second'\''" err
> +	grep "update_ref failed for ref '\''refs/heads/second'\''" err &&
> +
> +	cat >expect <<-\EOF &&
> +	Updated the following refs with --update-refs:
> +		refs/heads/first
> +		refs/heads/no-conflict-branch
> +		refs/heads/third
> +	Failed to update the following refs with --update-refs:
> +		refs/heads/second
> +	EOF
> +
> +	# Clear "Rebasing (X/Y)" progress lines and drop leading tabs.
> +	tail -n 6 err >err.last &&
I'm curious as to why we need tail here but not in the test above.
This is looking good, I'd be happy enough to see it merged as is.
Best Wishes
Phillip
Show 6 quoted lines
> +	sed -e "s/Rebasing.*Successfully/Successfully/g" -e "s/^\t//g" \
> +		<err.last >err.trimmed &&
> +	test_cmp expect err.trimmed
>   '
>   
>   # This must be the last test in this file
Previous: Derrick Stolee via GitGitGadgetNext: Derrick Stolee
Message 114 of 144 in “rebase: update branches in multi-part topic”
  1. 0/4 rebase: update branches in multi-part topicDerrick Stolee via GitGitGadget, Jun 3, 2022
  2. 2/4 branch: add branch_checked_out() helperDerrick Stolee via GitGitGadget, Jun 3, 2022
  3. Junio C HamanoJun 3, 2022
  4. 1/4 log-tree: create for_each_decoration()Derrick Stolee via GitGitGadget, Jun 3, 2022
  5. Junio C HamanoJun 3, 2022
  6. Derrick StoleeJun 3, 2022
  7. Junio C HamanoJun 3, 2022
  8. 3/4 rebase: add --update-refs optionDerrick Stolee via GitGitGadget, Jun 3, 2022
  9. Phillip WoodJun 7, 2022
  10. 4/4 rebase: add rebase.updateRefs config optionDerrick Stolee via GitGitGadget, Jun 3, 2022
  11. Junio C HamanoJun 3, 2022
  12. Taylor BlauJun 3, 2022
  13. Junio C HamanoJun 3, 2022
  14. Jeff HostetlerJun 3, 2022
  15. Taylor BlauJun 3, 2022
  16. Junio C HamanoJun 3, 2022
  17. Phillip WoodJun 4, 2022
  18. Derrick StoleeJun 6, 2022
  19. Phillip WoodJun 7, 2022
  20. Derrick StoleeJun 7, 2022
  21. Junio C HamanoJun 8, 2022
  22. Junio C HamanoJun 6, 2022
  23. Elijah NewrenJun 7, 2022
  24. 0/7 rebase: update branches in multi-part topicDerrick Stolee via GitGitGadget, Jun 7, 2022
  25. 1/7 log-tree: create for_each_decoration()Derrick Stolee via GitGitGadget, Jun 7, 2022
  26. 3/7 sequencer: define array with enum valuesDerrick Stolee via GitGitGadget, Jun 7, 2022
  27. Junio C HamanoJun 7, 2022
  28. 2/7 branch: add branch_checked_out() helperDerrick Stolee via GitGitGadget, Jun 7, 2022
  29. Junio C HamanoJun 7, 2022
  30. Derrick StoleeJun 8, 2022
  31. Derrick StoleeJun 8, 2022
  32. Junio C HamanoJun 8, 2022
  33. 4/7 sequencer: add update-refs commandDerrick Stolee via GitGitGadget, Jun 7, 2022
  34. 6/7 sequencer: implement 'update-refs' commandDerrick Stolee via GitGitGadget, Jun 7, 2022
  35. Junio C HamanoJun 7, 2022
  36. 5/7 rebase: add --update-refs optionDerrick Stolee via GitGitGadget, Jun 7, 2022
  37. 7/7 rebase: add rebase.updateRefs config optionDerrick Stolee via GitGitGadget, Jun 7, 2022
  38. Phillip WoodJun 8, 2022
  39. Derrick StoleeJun 8, 2022
  40. Phillip WoodJun 9, 2022
  41. 0/8 rebase: update branches in multi-part topicDerrick Stolee via GitGitGadget, Jun 28, 2022
  42. 1/8 t2407: test branches currently using apply backendDerrick Stolee via GitGitGadget, Jun 28, 2022
  43. Junio C HamanoJun 28, 2022
  44. Derrick StoleeJun 29, 2022
  45. Junio C HamanoJun 30, 2022
  46. Derrick StoleeJun 30, 2022
  47. 8/8 rebase: add rebase.updateRefs config optionDerrick Stolee via GitGitGadget, Jun 28, 2022
  48. 6/8 rebase: add --update-refs optionDerrick Stolee via GitGitGadget, Jun 28, 2022
  49. Junio C HamanoJun 28, 2022
  50. Derrick StoleeJun 29, 2022
  51. Phillip WoodJul 1, 2022
  52. Elijah NewrenJul 1, 2022
  53. Derrick StoleeJul 4, 2022
  54. Elijah NewrenJul 4, 2022
  55. Derrick StoleeJul 5, 2022
  56. Elijah NewrenJul 8, 2022
  57. 7/8 rebase: update refs from 'update-ref' commandsDerrick Stolee via GitGitGadget, Jun 28, 2022
  58. Junio C HamanoJun 28, 2022
  59. Derrick StoleeJun 29, 2022
  60. Junio C HamanoJun 30, 2022
  61. Derrick StoleeJun 29, 2022
  62. Phillip WoodJul 1, 2022
  63. Junio C HamanoJul 1, 2022
  64. Elijah NewrenJul 1, 2022
  65. Derrick StoleeJul 4, 2022
  66. 5/8 sequencer: add update-ref commandDerrick Stolee via GitGitGadget, Jun 28, 2022
  67. Phillip WoodJun 30, 2022
  68. 4/8 sequencer: define array with enum valuesDerrick Stolee via GitGitGadget, Jun 28, 2022
  69. Junio C HamanoJun 28, 2022
  70. 2/8 branch: consider refs under 'update-refs'Derrick Stolee via GitGitGadget, Jun 28, 2022
  71. Junio C HamanoJun 28, 2022
  72. Derrick StoleeJun 29, 2022
  73. Phillip WoodJun 30, 2022
  74. Junio C HamanoJun 30, 2022
  75. Junio C HamanoJun 30, 2022
  76. Phillip WoodJun 30, 2022
  77. Derrick StoleeJun 30, 2022
  78. Phillip WoodJul 1, 2022
  79. 3/8 rebase-interactive: update 'merge' descriptionDerrick Stolee via GitGitGadget, Jun 28, 2022
  80. Junio C HamanoJun 28, 2022
  81. Derrick StoleeJun 29, 2022
  82. Junio C HamanoJun 30, 2022
  83. Phillip WoodJun 30, 2022
  84. Junio C HamanoJun 28, 2022
  85. Phillip WoodJul 1, 2022
  86. 00/12 rebase: update branches in multi-part topicDerrick Stolee via GitGitGadget, Jul 12, 2022
  87. 01/12 t2407: test bisect and rebase as black-boxesDerrick Stolee via GitGitGadget, Jul 12, 2022
  88. 02/12 t2407: test branches currently using apply backendDerrick Stolee via GitGitGadget, Jul 12, 2022
  89. 03/12 branch: consider refs under 'update-refs'Derrick Stolee via GitGitGadget, Jul 12, 2022
  90. Phillip WoodJul 15, 2022
  91. 05/12 sequencer: define array with enum valuesDerrick Stolee via GitGitGadget, Jul 12, 2022
  92. 04/12 rebase-interactive: update 'merge' descriptionDerrick Stolee via GitGitGadget, Jul 12, 2022
  93. 06/12 sequencer: add update-ref commandDerrick Stolee via GitGitGadget, Jul 12, 2022
  94. 07/12 rebase: add --update-refs optionDerrick Stolee via GitGitGadget, Jul 12, 2022
  95. Elijah NewrenJul 16, 2022
  96. Derrick StoleeJul 19, 2022
  97. SZEDER GáborJul 18, 2022
  98. Derrick StoleeJul 18, 2022
  99. Junio C HamanoJul 18, 2022
  100. Derrick StoleeJul 19, 2022
  101. Junio C HamanoJul 19, 2022
  102. Derrick StoleeJul 19, 2022
  103. 08/12 rebase: update refs from 'update-ref' commandsDerrick Stolee via GitGitGadget, Jul 12, 2022
  104. Phillip WoodJul 15, 2022
  105. Derrick StoleeJul 19, 2022
  106. 09/12 sequencer: rewrite update-refs as user edits todo listDerrick Stolee via GitGitGadget, Jul 12, 2022
  107. Phillip WoodJul 15, 2022
  108. Derrick StoleeJul 15, 2022
  109. Phillip WoodJul 18, 2022
  110. Elijah NewrenJul 16, 2022
  111. 11/12 sequencer: ignore HEAD ref under --update-refsDerrick Stolee via GitGitGadget, Jul 12, 2022
  112. 10/12 rebase: add rebase.updateRefs config optionDerrick Stolee via GitGitGadget, Jul 12, 2022
  113. 12/12 sequencer: notify user of --update-refs activityDerrick Stolee via GitGitGadget, Jul 12, 2022
  114. Phillip WoodJul 15, 2022
  115. Derrick StoleeJul 15, 2022
  116. Elijah NewrenJul 16, 2022
  117. Elijah NewrenJul 16, 2022
  118. Derrick StoleeJul 19, 2022
  119. Junio C HamanoJul 12, 2022
  120. Derrick StoleeJul 14, 2022
  121. Junio C HamanoJul 14, 2022
  122. Elijah NewrenJul 16, 2022
  123. Elijah NewrenJul 16, 2022
  124. Phillip WoodJul 15, 2022
  125. 00/12 rebase: update branches in multi-part topicDerrick Stolee via GitGitGadget, Jul 19, 2022
  126. 01/12 t2407: test bisect and rebase as black-boxesDerrick Stolee via GitGitGadget, Jul 19, 2022
  127. 02/12 t2407: test branches currently using apply backendDerrick Stolee via GitGitGadget, Jul 19, 2022
  128. 03/12 branch: consider refs under 'update-refs'Derrick Stolee via GitGitGadget, Jul 19, 2022
  129. 04/12 rebase-interactive: update 'merge' descriptionDerrick Stolee via GitGitGadget, Jul 19, 2022
  130. 05/12 sequencer: define array with enum valuesDerrick Stolee via GitGitGadget, Jul 19, 2022
  131. 06/12 sequencer: add update-ref commandDerrick Stolee via GitGitGadget, Jul 19, 2022
  132. 07/12 rebase: add --update-refs optionDerrick Stolee via GitGitGadget, Jul 19, 2022
  133. 08/12 rebase: update refs from 'update-ref' commandsDerrick Stolee via GitGitGadget, Jul 19, 2022
  134. Phillip WoodJul 21, 2022
  135. 09/12 sequencer: rewrite update-refs as user edits todo listDerrick Stolee via GitGitGadget, Jul 19, 2022
  136. Phillip WoodJul 21, 2022
  137. 10/12 rebase: add rebase.updateRefs config optionDerrick Stolee via GitGitGadget, Jul 19, 2022
  138. 12/12 sequencer: notify user of --update-refs activityDerrick Stolee via GitGitGadget, Jul 19, 2022
  139. 11/12 sequencer: ignore HEAD ref under --update-refsDerrick Stolee via GitGitGadget, Jul 19, 2022
  140. Elijah NewrenJul 21, 2022
  141. Derrick StoleeJul 21, 2022
  142. Elijah NewrenJul 21, 2022
  143. Derrick StoleeJul 21, 2022
  144. Phillip WoodJul 21, 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.