question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Merge failed with "Unexpected diff result returned: '2'"

See original GitHub issue

Description

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

2019-01-09.desktop.production.log

Issue Analytics

  • State:open
  • Created 5 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
ms609commented, Jan 10, 2019

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.

0reactions
WojTherapycommented, Jan 30, 2019

Same issue here guys.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found