Merge failed with "Unexpected diff result returned: '2'"
See original GitHub issueDescription
I’m attempting to update my current branch from master, using the “Branch→Update from Master” menu item.
When I click this, it identifies two conflicting files. I’ve edited these in an external editor to remove the conflicts, and when I return to Github Desktop I see
Resolve conflicts before merging master into mybranch [tick] All conflicts resolved
When I click “Commit merge”, I see
Error [!] Unexpected diff result returned: ‘2’
When I click “Close”, I’m back to the “All conflicts resolved” screen; I end up in a loop until I abort the merge.
After aborting the merge, I’m able to commit my changes and push to origin; here’s the commit.
Version
- GitHub Desktop: 1.5.1
- Operating system: Microsoct Windows [10.0.17134.472]
Additional Information
I don’t have Folder Redirection enabled, to my knowledge.
Logs
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Git merge reports "Already up-to-date" though there is a ...
The "Already up-to-date" message shows up when the HEAD of the branch you are merging into is a parent of the chain of...
Read more >MR diff/changes view shows old commits/changes - GitLab
There are situations where a change in the source branch that is already present in the target branch is shown in the merge...
Read more >Diff Merge error: An error in cleardiffmrg has occurred ... - IBM
If this is an XML file use the XML Diff Merge tool instead. Doing the Diff Merge from the command line is also...
Read more >How to enable 3-way diff in BitBucket 7.0?
Using anything other than the most vanilla git workflow with the 2-way, 3-dot merge results in PRs with diffs that are inaccurate.
Read more >Advanced GIT — Merge, History & Diffs - faun.dev
@d9nich ・ Sep 14,2022 ・ 2 min read ・ 434 views. faun logo ... Automatic merge failed; fix conflicts and then commit the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @outofambit , thanks for looking into this. Yes, “mybranch” = “contour”. The SHA would have been
6598bae3dc3d78e214d72c55115899c2274873b1
as you said.LFS is an interesting suggestion, though no files that match the pattern in
.gitattributes
(i.e.\inst\doc\*
) would have been changed at any point, as far as I can see.No binary files seem to have been involved in the diff or update, though there are two uncommitted binary files that should not have been affected by the merge; they were there before and after the merge. Do let me know if there’s any more information I can supply.
Same issue here guys.