Re: [EGIT] Push to GitHub caused corruption

[John Bito <jwbito@gmail.com>]

Running git fsck -full on the repo that I pushed from is clean.
Here's the git fsck -full from GitHub
       <mojombo>       git fsck --full
       <mojombo>       broken link from tree
f4f9ecd1875938baa42467dfd6a8134d75fe5de4 to tree
57548924f1eca854dc8db00844f95d3de2c82957
       <mojombo>       broken link from tree
f4f9ecd1875938baa42467dfd6a8134d75fe5de4 to tree
3d1f74522c3e7c3c03390fae376446fda6eed306
       <mojombo>       missing tree 3d1f74522c3e7c3c03390fae376446fda6eed306
       <mojombo>       missing tree 57548924f1eca854dc8db00844f95d3de2c82957
       <mojombo>       dangling commit ab6ce47159c1eaff0e4bae19291679267de9f669

The repo on GitHub is back where it was before the push.  I have a
copy of the corrupt one from GitHub (358MB tar.gz).  If there's
something I can do that would help to improve JGit/EGit, please let me
know.

Thanks,
John

On Mon, Aug 10, 2009 at 23:10, Robin Rosenberg<robin.rosenberg@gmail.com> wrote:
> måndag 10 augusti 2009 23:46:34 skrev John Bito <jwbito@gmail.com>:
>> Using the 'release' build of EGit (0.4.9.200906240051) I pushed a
>> commit to GitHub.  After that, using git to pull, I get 'bad tree
>> object' resulting in 'remote: aborting due to possible repository
>> corruption on the remote side'.  I had a similar problem back in April
>> (using integration builds of 0.4.0).  I'm willing to investigate if
>> there's interest in finding the root of the problem.
>
> Fixing problems related to repository integrity is definitely interesting. One
> can live all kinds of problem, as long as they don't destroy anything.
>
> -- robin
>
>