Subject: Unable to fetch from private repo "bad tree object"
Original Post
Kim Pepper
I'm having trouble fetching from a private repo. I get the following error message:
git fetch -v error: Could not read b6648eac1dc57694b1de43ab9176277751d76afc fatal: bad tree object b6648eac1dc57694b1de43ab9176277751d76afc remote: Counting objects: 4, done. remote: Compressing objects: 100% (3/3), done. remote: Total 3 (delta 0), reused 0 (delta 0) remote: aborting due to possible repository corruption on the remote side. error: waitpid (async) failed fatal: git-upload-pack: aborting due to possible repository corruption on the remote side. Unpacking objects: 100% (3/3), done. error: waitpid (async) failed fatal: error in sideband demultiplexer
Comments are currently closed for this discussion. You can start a new one.
2 Posted by Kim Pepper on 09 Jun, 2009 11:06 PM
Repo is at https://github.com/previousnext/nsw-works/tree
3 Posted by Lukas Fittl on 18 Jun, 2009 10:27 PM
We're having the same problem with the public repository http://github.com/soup/rails/tree/2-3-stable (although we're fetching through the private clone url)
Log: http://gist.github.com/132247
Support Staff 4 Posted by Tom Preston-Werner on 19 Jun, 2009 03:02 AM
Kim, can you re-push your repo with tags? It looks like a server side corruption is causing a missing link. We're looking into the possible causes of this.
Support Staff 5 Posted by Tom Preston-Werner on 19 Jun, 2009 03:04 AM
Lukas, can you re-push your repo with tags? It looks like a server side corruption is causing a broken link. We're looking into the possible causes of this.
6 Posted by Lukas Fittl on 19 Jun, 2009 03:41 AM
Tom, doing a "git push --tags" results in the following errors: http://gist.github.com/132390
7 Posted by Lukas Fittl on 19 Jun, 2009 03:55 AM
Interestingly, doing a git-clone now resuls in a different error: http://gist.github.com/132401
And doing another "git push" returns the following: http://gist.github.com/132404
Thanks for your help!
Support Staff 8 Posted by Tekkub on 19 Jun, 2009 10:49 PM
Lukas, your issue is actually different from the original poster's. I applied a fix, but I'm not sure if your push before the fix caused issues. Are you able to push or pull now?
9 Posted by Lukas Fittl on 21 Jun, 2009 07:14 AM
Unfortunately there are still problems with the wip_abstract_controller branch: http://gist.github.com/133435
Interestingly there also was an 404 when accessing http://github.com/soup/rails/tree/2-3-stable before I issued "git push origin 2-3-stable".
http://github.com/soup/rails/tree/wip_abstract_controller still returns 404, "git push origin wip_abstract_controller" does not work (see pasted shell output).
10 Posted by Kim Pepper on 21 Jun, 2009 10:59 PM
We have abandoned the repo as it was for a project that need to go live quickly. Will there be any problems if I just delete the repo?
Support Staff 11 Posted by Tekkub on 22 Jun, 2009 07:16 AM
There shouldn't be an issue Kim. Sorry about the troubles, I'm not sure if Tom has found the cause yet.
Lukas, do you have a full clone of your fork locally? It might just be simplest at this point to re-fork and re-push.
12 Posted by Lukas Fittl on 22 Jun, 2009 06:22 PM
Did a re-fork, and re-push, works again (as expected).
Thanks for your help!
PS: Is there a particular reason why the rails/rails repository has a HEAD branch on github? That caused weird errors when cloning, until I deleted that branch on our fork.
Support Staff 13 Posted by Tekkub on 22 Jun, 2009 06:46 PM
It looks like HEAD is pointing to a branch, not a commit, as it should be. What error was it causing?
14 Posted by Lukas Fittl on 22 Jun, 2009 07:17 PM
Steps to repeat:
Support Staff 15 Posted by defunkt on 10 Jul, 2009 05:57 PM
We recently tweaked the Rails repo - this problem shouldn't happen anymore.
Cheers,
Chris