Issues

Issue #6402 resolved

recursion detected in die handler

arashbi
created an issue

I cannot push to my repo any more :

$ git push -v -u origin master
trace: built-in: git 'push' '-v' '-u' 'origin' 'master'
Pushing to git@bitbucket.org:arashbi/android-mind.git
trace: run_command: 'ssh' 'git@bitbucket.org' 'git-receive-pack '\''arashbi/andr
oid-mind.git'\'''
Enter passphrase for key '/c/Users/arash/.ssh/id_rsa':
trace: run_command: 'pack-objects' '--all-progress-implied' '--revs' '--stdout'
'--thin' '--delta-base-offset' '--progress'
trace: built-in: git 'pack-objects' '--all-progress-implied' '--revs' '--stdout'
 '--thin' '--delta-base-offset' '--progress'
Counting objects: 87, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (54/54), done.
Writing objects: 100% (61/61), 908.16 KiB, done.
Total 61 (delta 29), reused 0 (delta 0)
Read from remote host bitbucket.org: Connection reset by peer
fatal: The remote end hung up unexpectedly
fatal: recursion detected in die handler

Comments (8)

  1. Brian Nguyen

    Hi,

    Is this still a problem for you? Our servers were experiencing high load on Saturday that may have caused your issue pushing. This should be fixed now however.

    I looked into your repository, and it does not appear to be corrupted.

    Are you having these problems for any repository or just this one?

    Cheers, Brian

  2. arashbi reporter

    I still have that problem. If I checkout the repo afresh and make a change, I can commit. But I cannot commit my original changes from the local repo I have worked.

  3. Brian Nguyen

    Hi,

    Thanks for the information. Those symptoms seem very strange. If you can push from a separate clone, the problem could be a corrupt repository. Could you try running:

    git fsck
    

    In the meantime if you would like to push up your commits, you can apply a patch.

    In your original repository:

    git format-patch master --stdout > bitbucket.patch
    

    And in your clone:

    git am < fix_empty_poster.patch
    

    Cheers, Brian

  4. Log in to comment