git没有干净退出(退出代码128)写入错误:错误的文件描述符 [英] git did not exit cleanly (exit code 128) write error: Bad file descriptor

问题描述

几天以来，我一直无法在原点分支上对Github进行拉/推. 我在TortoiseGit中使用git.

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)

我认为这与我的本地工作树有关. 每次新提交"Working dir changes"

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 

我做了什么:

• TortoiseGit清理:
  清洁型
  • 删除所有未跟踪的文件(-fx)
  • 删除未跟踪的目录(-d)
  • TortoiseGit clean up:
    clean Type
    • Remove all untracked files (-fx)
    • Remove untracked directories (-d)

    如何在本地恢复一致的存储库?

    What can I do to recover a coherent repo locally?

    推荐答案

    如果是您的工作树/索引因某种原因损坏了，您可以:

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

    • 努力尝试，然后找到丢失的对象
    • 首先尝试简单的方法，然后再次将GitHub存储库克隆到另一个目录中.

    我会先尝试第二种方法.

    I would try the second approach first.

    这篇关于git没有干净退出(退出代码128)写入错误:错误的文件描述符的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！