Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gource does not follow log's timeline #27

Closed
GoogleCodeExporter opened this issue Apr 12, 2016 · 6 comments
Closed

Gource does not follow log's timeline #27

GoogleCodeExporter opened this issue Apr 12, 2016 · 6 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
Use attached log (which was converted from svn) with any settings

What is the expected output? What do you see instead?
The bug starts to appear in the log revision where I started removing almost 
every file. A huge 1 
day pause happenes, which the program doesn't skip (even with -a option). Also 
while the pause 
is in effect, the only user - me disappears, since he doesn't add anything. 
Later the bug repairs 
itself, (moves on to later logs, but the date is wrong), yet the user doesn't 
reappear, files appear 
on their own


What version of the product are you using? On what operating system?
Svn script 1.2 and Gource 0.22, and fully updated xp with sp2


Please provide any additional information below.
As I stated before, it's the conversion from svn, I can't understand the xml 
logs, so maybe there 
is a bug in a svn converter.
Also the svn was the latest version at that time.

Atttached files:
asd2.log - converted log
asd.log - svn log (--verbose --xml)

Original issue reported on code.google.com by olaf.tomalka on 20 Dec 2009 at 4:47

Attachments:

@GoogleCodeExporter
Copy link
Author

Hi. I don't think I'm seeing the same things. Seems to skip ahead ok, no files
appearing on their own.

asd2.log appears to contain empty directories (these show up as white files 
with the
directory name in Gource) which you could remove if you use the svn-gource.py
--filter-dirs option.

Since your log is for a short period maybe use --realtime or -s 24 as the 
default is
3 days a second, which is too fast.

Hope this helps.

Original comment by acaudw...@gmail.com on 21 Dec 2009 at 11:09

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

Ekhm, I've made a mistake, it seems that the bug only appears on high -s 
parameter
(it showed on 1024), it surely appears on this parameters "gource.exe -800x600 
-a 1
-s 1024 --highlight-user Ritave asd2.log", I tried many combinations and the 
only
thing that matters is -s parameter.
If the bug still doesn't show up on your computer I've included a movie showing 
it.

Original comment by olaf.tomalka on 21 Dec 2009 at 1:37

Attachments:

@GoogleCodeExporter
Copy link
Author

Hi. I'm not sure this is a bug. It's reached the end of your log and then the 
files
start to disappear as they expire from inactivity.

If you want Gource to exit when it gets to the end of your log you can add:

--stop-position 1.0

(while looking into this it appears I've broken the --stop-on-idle option so I 
might
need to look into that)

Original comment by acaudw...@gmail.com on 21 Dec 2009 at 8:51

@GoogleCodeExporter
Copy link
Author

O.o that's even weirder, since my svn log has entries which point that I 
actually
removed all of the files, and then re added some (which is true), and that 
means -
they were removed from saved svn log, or lost while changing it to git log. 
Actually
I've waited before (by mistake) on some other log after the progress has ended 
and
the files didn't start disappearing.
Anyways if the automatic file is expected, can it be more documented in options 
please?

Original comment by olaf.tomalka on 21 Dec 2009 at 9:57

@GoogleCodeExporter
Copy link
Author

Original comment by acaudw...@gmail.com on 9 Jul 2010 at 2:32

  • Changed state: Done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant