"Elijah Newren via GitGitGadget" <gitgitgadget@xxxxxxxxx> writes:
> Fix the main problem by making sure that restore_state() only skips the
> stash application if the stash is null rather than skipping the whole
> function.
OK.
> However, there is a secondary problem -- since merge.c forks
> subprocesses to do the cleanup, the in-memory index is left out-of-sync.
> While there was a refresh_cache(REFRESH_QUIET) call that attempted to
> correct that, that function would not handle cases where the previous
> merge strategy added conflicted entries. We need to drop the index and
> re-read it to handle such cases.
Absolutely right.
> diff --git a/builtin/merge.c b/builtin/merge.c
> index aaee8f6a553..a21dece1b55 100644
> --- a/builtin/merge.c
> +++ b/builtin/merge.c
> @@ -385,11 +385,11 @@ static void restore_state(const struct object_id *head,
> {
> const char *args[] = { "stash", "apply", "--index", NULL, NULL };
>
> - if (is_null_oid(stash))
> - return;
> -
> reset_hard(head, 1);
>
> + if (is_null_oid(stash))
> + goto refresh_cache;
> +
> args[3] = oid_to_hex(stash);
>
> /*
> @@ -398,7 +398,9 @@ static void restore_state(const struct object_id *head,
> */
> run_command_v_opt(args, RUN_GIT_CMD);
>
> - refresh_cache(REFRESH_QUIET);
> +refresh_cache:
> + if (discard_cache() < 0 || read_cache() < 0)
> + die(_("could not read index"));
Don't we need refresh_cache() after re-reading the on-disk index, or
do we have nothing to do further after restore_state() returns and
the stat-info being stale does not matter? Given that [3/6] exists,
I suspect that we do want to make sure the in-core index is refreshed
before we go ahead and run the next merge, no?
> }
>
> /* This is called when no merge was necessary. */
> diff --git a/t/t7607-merge-state.sh b/t/t7607-merge-state.sh
> new file mode 100755
As long we are adding a brand-new script for new tests, probably we
should add tests for other steps (like [4/6]) here, perhaps?
> index 00000000000..655478cd0b3
> --- /dev/null
> +++ b/t/t7607-merge-state.sh
> @@ -0,0 +1,25 @@
> +#!/bin/sh
> +
> +test_description="Test that merge state is as expected after failed merge"
> +
> +GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME=main
> +export GIT_TEST_DEFAULT_INITIAL_BRANCH_NAME
> +. ./test-lib.sh
> +
> +test_expect_success 'set up custom strategy' '
> + test_commit --no-tag "Initial" base base &&
> +git show-ref &&
Is this part of the test, or a leftover debugging aid?
> +
> + for b in branch1 branch2 branch3
> + do
> + git checkout -b $b main &&
> + test_commit --no-tag "Change on $b" base $b
> + done &&
> +
> + git checkout branch1 &&
> + test_must_fail git merge branch2 branch3 &&
> + git diff --exit-code --name-status &&
> + test_path_is_missing .git/MERGE_HEAD
> +'
Hmph, I am not sure if the new behaviour is not too pessimistic.
When octopus fails after successfully merging branch2 and then
failing the merge of branch3 (i.e. the last one) due to conflict,
I think octpus users are used to be able to resolve it manually
and make a commit. Are we making it impossible by doing the
reset-restore dance here?
I do not use, and more importantly, I do not recommend others to
use, Octopus anymore, and from that point of view, it is a good move
to make Octopus harder to use on any non-trivial merge, but those
who still like Octopus may disagree.
Thanks.
> +test_done
