Issue #8958 resolved

Cannot Push

Chris MacNaughton
created an issue
Counting objects: 19, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 8.20 KiB | 0 bytes/s, done.
Total 11 (delta 7), reused 0 (delta 0)
remote: fatal: unresolved deltas left after unpacking
error: unpack failed: unpack-objects abnormal exit
To ssh://git@bitbucket.org/user/repo.git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'ssh://git@bitbucket.org/user/repo.git'

Comments (8)

  1. Chris MacNaughton reporter

    Likely related, when I try to clone to a new directory, I get

    remote: error: Could not read d18002a0da92b3b4f7555ad3d243548c0ff362b9
    remote: fatal: Failed to traverse parents of commit b171a738ab6a1c33ecd345d7fd6c08b7e56a9d27
    error: git upload-pack: git-pack-objects died with error.
    fatal: git upload-pack: aborting due to possible repository corruption on the remote side.
    remote: aborting due to possible repository corruption on the remote side.
    fatal: early EOF
    fatal: index-pack failed
    
  2. Jon Mooring staff

    We are currently investigating an issue affecting a small percentage of repositories on Bitbucket. We’ve temporarily placed your repository into read-only mode while we are investigating this issue.

  3. Justen Stepka

    Hi everyone,

    Yesterday during maintenance a small number of repositories were temporarily taken offline. We have now restored access to most these repositories.

    If you are still experience problems, could you please open a support ticket by emailing support@bitbucket.org with your specifics we will address your concerns ASAP. We apologize for any inconvenience this may have caused you and your team.

    Cheers, Justen -- Bitbucket product manager

  4. Jon Mooring staff

    I'm closing this issue for now. If you continue to experience difficulties, please feel free to re-open it or contact Support at support@bitbucket.org.

    Thanks,
    Jon

  5. Log in to comment