git did not exit cleanly (exit code 128) write error: Bad file descriptor

Question

Since a couple of days I have a problem to pull/push on Github on the origin branch. I use git with TortoiseGit.

I got this error message on push:

fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
fatal: write error: Bad file descriptor

I got this error message on pull:

git.exe pull -v --progress       "origin"
Cannot chdir to , the toplevel of the working tree

git did not exit cleanly (exit code 1) (6771 ms @ 20.09.2013 10:01:25)

And I think it has to do with my local working tree. the view of the commit log shows in the top row after every new commit "Working dir changes"

in below in the description area there stands:

SHA-1: 000000000000000000000000000000000000000

Working dir changes 
files changed

What I have done:

TortoiseGit clean up:
clean Type
- Remove all untracked files (-fx)
- Remove untracked directories (-d)

What can I do to recover a coherent repo locally?

Community · Accepted Answer · 2017-05-23 12:22:58Z

1

IF it is your working tree/index which is somehow corrupted, you could:

try the hard way, and find the missing objects
try the easy way first, and clone again your GitHub repo in a different directory.

I would try the second approach first.

edited May 23, 2017 at 12:22

CommunityBot

11 silver badge

answered Sep 22, 2013 at 0:29

VonC

1.4m569 gold badges4.8k silver badges5.7k bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

git did not exit cleanly (exit code 128) write error: Bad file descriptor

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related