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.

Getting error (Git returned an unexpected exit code '128') after updating to v1.3.1

See original GitHub issue

Description

Few minutes ago I’ve updated to v1.3.1 and after opening GitHub Desktop (everytime) I get this error pops up.

Version

  • GitHub Desktop: 1.3.1
  • Operating system: Windows 10 x64

Steps to Reproduce

  1. Update to v1.3.1
  2. Open Desktop. You get error.
  3. Close and re-open Desktop.
  4. You will get this error again.

You will also get this error if you keep GitHub Desktop open. Probably a background task.

Expected Behavior

No error should raised.

Actual Behavior

Git returned an unexpected exit code '128' which should be handled by the caller.'

Additional Information

No additional info

Logs

I could attach log here but I investigated it and no error or similar messages but infos available. I avoid uploading all logs here due to some details about my private repositories in it.

Update: This evening I keep GitHub Desktop open in the background. After 5-6 hours, when I maximize it, I see error message already displayed. I just clicked Close however, another one pops up. I tried nearly hundred times and it seems GitHub Desktop does this in a loop in the background, so I got probably a thousand of errors. I had to close manually from task manager. Anyway, I just watch my GitHub Desktop today and it’s indeed this error pops up every few minutes.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:7
  • Comments:13 (5 by maintainers)

github_iconTop GitHub Comments

5reactions
manogicommented, Jul 31, 2018

I have exactly the same issue on Mac OSX 10.13.6.

The Error: Git returned an unexpected exit code ‘128’ which should be handled by the caller.’

I also only see the expected log entries - only infos, some warnings, no errors and nothing that seems related to this.

image

3reactions
shiftkeycommented, Jul 31, 2018

Just a heads up for people who are arriving to this issue - the PR #5297 has been merged, but we’re just looking to wrap up #5300 and aiming to publish a release tomorrow. Stay tuned.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to resolve "git did not exit cleanly (exit code 128)" error ...
exit code 128 means a lot of things. In my case, the destination path where the project is cloning is "long". I tried...
Read more >
Build fails with "Git fetch failed with exit code: 128" error with ...
Specifically when I have configured VSTS's Bitbucket Cloud connection to use "Grant" authorization via Oath.
Read more >
"git did not exit cleanly (exit code 128)" error, even after ...
Got the error "git did not exit cleanly (exit code 128)". This errors persists even after a restart, and on different repositories that...
Read more >
Clink v1.4.6 - GitHub Pages
When this is enabled, Clink runs a hidden echo %errorlevel% command before each interactive input prompt to retrieve the last exit code for...
Read more >
Changelog - Sourcegraph docs
#45918; Git blame view got a user-interface overhaul and now shows data in a ... Fixed an issue causing context cancel error dumps...
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