Hi Jeroen, thank you for for tracing that. It is fixed now in the master branch.
Cheers, Pawel On 30 April 2014 14:42, Jeroen Muis <[email protected]> wrote: > Hi, > > I've created an issue at: > https://gitorious.org/projects/gitorious/issues/444 > as we now have a reproducible issue. It's caused by any empty commit > message. > > Confirmed by executing git filter-branch after which the issue disappears. > > $ git filter-branch --msg-filter ' > message=`cat` > if [ "$message" == "" ]; > then > message="empty" > fi > echo "$message" > ' -- --all > > > > > On Tue, Apr 29, 2014 at 2:45 PM, Jeroen Muis <[email protected]>wrote: > >> Hi, >> >> Most likely I found the issue. >> The initial commit (again, converted from Mercurial) has no files and an >> empty commit message. Please, don't ask why and how :) >> >> I can imagine, this might somehow be an issue for gitorious as there is >> 'not so much' to be displayed when the commit message is empty. >> To confirm I need to strip out this commit, but as it's the root commit >> GIT keeps complaining to me. >> >> I've tried to google it for a solution, but not much lock so far, as the >> original commit seems to be pretty persistent. >> Do you (or someone else) happen to know how to get this job done? I now >> it's a (little) off-topic, but most likely this is causing the tree not to >> display properly as the other repos don't have such commits. >> >> Brgds, >> Jeroen >> >> >> >> >> On Tue, Apr 29, 2014 at 9:00 AM, Jeroen Muis <[email protected]>wrote: >> >>> Hi Pawel, >>> >>> Sounds like a lot of work indeed. >>> I believe I do have some small repo containing this issue, so let me >>> sort it and revert as soon as I have some update on this topic. >>> FYI the are originating from Mercurial and have been converted to GIT. >>> >>> Thanks for your help so far. >>> Jeroen >>> >>> >>> >>> On Mon, Apr 28, 2014 at 4:07 PM, Paweł Pierzchała >>> <[email protected]>wrote: >>> >>>> Hi Jeroen, >>>> I would start with creating another repo with a clone, firstly I would >>>> remove all the branches except master to find whether the issue is related >>>> to branching or specific commit in history. >>>> >>>> If the tree view works, then I would try to find the broken branch by >>>> adding them back until tree view is broken again. >>>> >>>> In the tree view would still be broken, I would try with git bisect to >>>> find the broken commit. >>>> >>>> Finally, I would try to create a repo that would include a >>>> commit/branch broken in a similar way to the one found. That is a lot of >>>> effort to just reproduce the issue, depending how much you need the tree >>>> view you might want to do it. >>>> >>>> Cheers, >>>> Pawel >>>> >>>> >>>> On 25 April 2014 14:52, <[email protected]> wrote: >>>> >>>>> Hi Pawel, >>>>> >>>>> Thanks for your reply. >>>>> [We are accessing the 'source code' tab through the following URLs: >>>>> https://git.copasbv.lan/edi/edistep/source/master: >>>>> >>>>> https://git.copasbv.lan/copas/activitygrid/source/bf31463f959d09805ebcf99e2bd0f7e030b681a1 >>>>> : >>>>> >>>>> And yes, it's always the same repos with this issue, and yes, all the >>>>> time. None of the other repos are failing. >>>>> >>>>> Any thoughts on how to prepare a single repos with this issue, as I >>>>> can't share my entire installation with you as it contains quite a bit of >>>>> proprietary code. >>>>> >>>>> Best regards, >>>>> Jeroen Muis >>>>> >>>>> On Thursday, April 24, 2014 3:02:27 PM UTC+2, Paweł Pierzchała wrote: >>>>> > Hi Jeroen, >>>>> > >>>>> > I haven't seen that error before, so I need more details. How are >>>>> you accessing the tree history (gitorious.local/project/repository/graph)? >>>>> Does it happen all the time for the same repos? Could you prepare a >>>>> repository with a broken tree history, so we could reproduce it? >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > Cheers, >>>>> > Pawel >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > On 15 April 2014 08:58, <[email protected]> wrote: >>>>> > >>>>> > >>>>> > Hi, >>>>> > >>>>> > >>>>> > >>>>> > We recently started using Gitorious for managing our GIT >>>>> repositories and so far everything is running really well. Our setup seems >>>>> to be pretty ok (Centos 6.5 / ce_installer) as push / fetch / branching >>>>> and tagging all works. >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > However on some repos(not all!) the tree history doesn't load and >>>>> fails with a javascript 'undefined' anonymous function error in the >>>>> console. (The loading icon keeps displaying) where on repos we do get tree >>>>> history for the console doesn't log the exception. >>>>> > >>>>> > >>>>> > >>>>> > Tried multiple browsers (chrome / firefox and even IE) but none of >>>>> them works. >>>>> > >>>>> > >>>>> > >>>>> > Anyone seen this before or has a clue how to resolve? >>>>> > >>>>> > >>>>> > >>>>> > Your help is really appreciated! >>>>> > >>>>> > Jeroen Muis >>>>> > >>>>> > >>>>> > >>>>> > -- >>>>> > >>>>> > -- >>>>> > >>>>> > To post to this group, send email to [email protected] >>>>> > >>>>> > To unsubscribe from this group, send email to >>>>> > >>>>> > [email protected] >>>>> > >>>>> > >>>>> > >>>>> > --- >>>>> > >>>>> > You received this message because you are subscribed to the Google >>>>> Groups "Gitorious" group. >>>>> > >>>>> > To unsubscribe from this group and stop receiving emails from it, >>>>> send an email to [email protected]. >>>>> > >>>>> > For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> -- >>>>> -- >>>>> To post to this group, send email to [email protected] >>>>> To unsubscribe from this group, send email to >>>>> [email protected] >>>>> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Gitorious" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>>> -- >>>> To post to this group, send email to [email protected] >>>> To unsubscribe from this group, send email to >>>> [email protected] >>>> >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Gitorious" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/gitorious/BJIWpbILfjA/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> > -- > -- > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > > --- > You received this message because you are subscribed to the Google Groups > "Gitorious" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] --- You received this message because you are subscribed to the Google Groups "Gitorious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
