Re: Stack overflow at write_one()

From: Shawn Pearce <spearce@spearce.org>
Date: Nov 20, 2011, 02:00 UTC
Message-ID: <CAJo=hJtBKmf_yuJDXoKPA7OXrXhaZtm+P6rQx1376dngAmQNiA@mail.gmail.com>
In-Reply-To: <4EC8437C.6000808@cesarb.net>

On Sat, Nov 19, 2011 at 16:02, Cesar Eduardo Barros <cesarb@cesarb.net> wrote:

Show 24 quoted lines

> Em 19-11-2011 21:30, Shawn Pearce escreveu:
>>
>> On Sat, Nov 19, 2011 at 13:46, Cesar Eduardo Barros<cesarb@cesarb.net>
>>  wrote:
>>>
>>> Em 19-11-2011 19:08, Junio C Hamano escreveu:
>>>>
>>>> Already found the real cause (jGit bug) and workaround posted, I think.
>>>
>>> I presume the cause then is what was fixed by
>>>
>>> http://egit.eclipse.org/w/?p=jgit.git;a=commit;h=2fbf296fda205446eac11a13abd4fcdb182f28d9
>>> ?
>>
>> Yes. The AOSP servers were all updated with the above JGit patch, so
>> the servers are no longer sending duplicate objects. But yes, for a
>> period of time there were duplicates in the kernel repositories,
>> particularly kernal/omap.
>
> So, would an alternative workaround in my situation be to delete
> kernel/omap.git and let repo sync recreate it? It seems repo does not have
> extra metadata anywhere else, so just removing the directory should be
> enough for it to clone again from scratch, hopefully getting a corrected
> pack from the server.

Yes. repo does not have extra state, so just removing the directory and running `repo sync` again to clone the repository would correct the local repository.