[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] Missing tree/blob <hash> when trying to push
|
The ‘unhandled loop exceptions’ are when a plugin throws an error and it gets propagated back up to the Eclipse platform instead of being caught by the plug-in that generated them. They may be related (especially if it suggests they are in an org.eclipse.egit or org.eclipse.jgit plug-in) but equally it could be some other plug-in generating them. If it’s something like ‘no more handles’ or a memory condition it suggests there may be an swt/memory leak in one of the installed plug-ins.
Alex
On 17 Oct 2014, at 12:17, Andrew Eidsness <eclipse@xxxxxxxxxx> wrote:
> Thanks for the quick reply!
>
> I'm not sure what you mean by "kind of git server". Here is a list of things that it could mean, but let me know if you
> mean something different. Starting from the bottom, it is a Xeon running Ubuntu 12.04. It has git version 1.7.9.5 and
> Gerrit version 2.8.6.1. We use Gerrit as the interface to git, all pulls are from a Gerrit-based URL and all pushes are
> to changesets created in Gerrit. We're both using the same version of Eclipse and we specifically checked our EGit and
> JGit versions to confirm they were identical.
>
> His use case isn't very involved, and I've tried the same steps on my machine. It is something that I do frequently
> without problems. His steps are really just "amend a changeset and try to push again".
>
> One other thing that I forgot to add to the initial description. He sees alot of "Unhandled loop" exceptions. Is there
> any way this could be related? I could get the stack trace from him if needed.
>
> -Andrew
>
> On 14-10-17 07:06 AM, Christian Halstrick wrote:
>> There have been a lot of mails regarding this. But since we are
>> talking about traces and debug output from Sascha's closed source
>> repository we couldn't talk about that on the public mailing list. But
>> any input from other people facing the same problem is of course very
>> helpful.
>>
>> Some questions around your case:
>> - which kind of git server are you using
>> - is it somehow possible that the user who always sees this problem
>> can try his use case from your machine
>>
>> Ciao
>> Chris
>>
>
> _______________________________________________
> egit-dev mailing list
> egit-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/egit-dev
