#3258 Fedorahosted.org trac timeline not working
Closed: Fixed None Opened 12 years ago by jerboaa.

= bug description =
Something changed since the latest trac upgrade. For some reason trac's timeline feature does not work anymore.

Go to: https://fedorahosted.org/eclipse-fedorapackager/timeline and you'll see

{{{
Event provider ChangesetModule failed for filters "Repository changesets": ValueError: invalid literal for int() with base 10: '<'
}}}

Timeline for other events works. It looks like it may be related to the SCM (Git) integration.

Thanks for looking into this!


It seems your last commit has a time of:

1970-01-01

which is causing trac to puke. ;(

See: http://git.fedorahosted.org/git/?p=eclipse-fedorapackager.git

Is there any way you can amend that commit with the correct time?

I have no idea where gitweb is taking the time from. On my local copy of the repo the git log timestamp is April 25 of commit !0c9b84b760ed3605bdeb9fb4875ed13c3b4a086d. So I don't think amending would help much. If I really need to amend it would be good to know if there is a theoretical chance of it fixing it (as it requires you to disable the force push prevention hook for master first and then me forcefully pushing it).

This shows April 25 as commit date for the offending log entry:
{{{
git clone git://git.fedorahosted.org/git/eclipse-fedorapackager.git
cd eclipse-fedorapackager
git show 0c9b84b760ed3605bdeb9fb4875ed13c3b4a086d
}}}

Could it be that there is some other problem (server side?) which causes the time to show up wrong? Thoughts? BTW: Since yesterday's outage fedorahosted.org seems to have slowed down. Very weird...

It could have been something strange on the server side, but not sure what. ;(

It's:

committer <>
Thu, 1 Jan 1970 00:00:00 +0000 (00:00 -0000)

thats messed up, so if an amend can change committer and time there it would fix it.

I'll ask around and see if there's any git savvy folks who can see a way to easily fix this.

ok, can we try this:

I will enable fast forward commits.
You run:

{{{
git filter-branch --env-filter \
'if [ $GIT_COMMIT = 0c9b84b760ed3605bdeb9fb4875ed13c3b4a086d ]
then
export GIT_AUTHOR_DATE="Wed Apr 25 14:50:40 2012 -0400"
export GIT_COMMITTER_DATE="Wed Apr 25 14:50:40 2012 -0400"
fi'
}}}

and push. Then we disable fast forwards again and confirm that the date is correct.

Let me know if that sounds ok and when you are ready? (either here or on #fedora-admin on irc).

OK, so I've ran the above filter which fixed the new line in the committer name field. In order to then fix the "committer" prefix I've used this filter (using this directly on the broken commit failed):

{{{
git filter-branch -f --env-filter 'if [ $GIT_COMMIT = 44fd5b8d69ccfba291c8e21030bca67087a5024a ]
then
export GIT_AUTHOR_NAME="Severin Gehwolf"
export GIT_AUTHOR_EMAIL="sgehwolf@redhat.com"
export GIT_COMMITTER_NAME="Severin Gehwolf"
export GIT_COMMITTER_EMAIL="sgehwolf@redhat.com"
fi'
}}}

Now the commit should should be fixed. Let's try to push this.

Login to comment on this ticket.

Metadata