Time doesn't match log

[GoogleCodeExporter]

What steps will reproduce the problem?
1. run gource on a project you worked
2.
3.

What is the expected output? What do you see instead?
I expect not to work between 21:00 to 06:00
I see the most of the activity in that range of time which I'm sure I've
not worked on the project. (I see my user floating around at those times)

What version of the product are you using? On what operating system?
0.11 on debian Linux i386

Please provide any additional information below.

Git version 1.5.6.5

May be some Locale time issue? I'm in Italy, so I don't expect this to be
greenwich time (should only be 1-2 hours of difference)

My repo is a git-svn repo, I don't know if this information is useful to you.

Software is pretty cool anyway, Just hope to help filing this bug report :)

Another things I noticed is that when I reach today the animation keep
going "in the future" and it seems that it is repeating the whole animation
from the beginning but faster. May be this is not a bug or it is "another bug".

Original issue reported on code.google.com by daniele....@gmail.com on 16 Sep 2009 at 7:50

[GoogleCodeExporter]

Yes it's probably not handling the locale / time zone information correctly.

Also sounds like a bug in the loop behavior when it reaches the end of the log.

Thanks for the report.

Original comment by acaudw...@gmail.com on 16 Sep 2009 at 8:06

• Changed state: Accepted

[GoogleCodeExporter]

I see this as well. The problem becomes more pronounced if you allow for less 
than 1
second per
day:http://github.com/dscho/Gource/commit/271e3d16c98c85da35973bba89fbde2b7949fc
4a

Running it on our 9 year old CVS repository. The log file from cvs-exp is 25MB.
Running it with 0.01 seconds per day, so it should only take ~30 seconds. 
However, it
takes a lot longer. The timestamp at the top is up to 2061 as I type this. The
progress bar always has the correct timestamp though. 

Very cool tool though. Our office is about to enter a huge debate about what 
version
control system to use (switching from CVS so anything is better). But the tool 
is
helping me to see interesting activity patterns. 

-Brian

Original comment by col...@gmail.com on 17 Sep 2009 at 1:16

[GoogleCodeExporter]

I think I've fixed the bug in the looping behavior. It should correctly reset 
to the
start of the log now.

I'm not sure there's a bug in the time display:

There is some amount of artistic license with the speed at which the user 
avatars
move and do commits so that you can see what's going on. For instance, a commit 
of
100 files while in reality happened instantly instead it is spread out over 5-10
seconds you can see 'hey that guy is really busy' and actually see what they're
doing. Replaying the log really fast (small values of seconds-per-day) fast will
naturally exacerbate this.

If you want realistic commit times, perhaps use --seconds-per-day 86400 
(real-time)
with --auto-skip-seconds 1 (so it skips ahead if nothing is going on).

Original comment by acaudw...@gmail.com on 18 Sep 2009 at 2:55

• Changed state: Fixed

[GoogleCodeExporter]

good, I suggest you to write that on the documentation :)
because I will not be the only one noticing avatars working at night :P

thanks for the suggestion and compliments for the software

Original comment by daniele....@gmail.com on 18 Sep 2009 at 7:03

[GoogleCodeExporter]

You're welcome

Original comment by acaudw...@gmail.com on 18 Sep 2009 at 8:19