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

Trouble with --start-date. timezone? #278

Open
pietsoftwaretogo opened this issue Jan 19, 2022 · 2 comments
Open

Trouble with --start-date. timezone? #278

pietsoftwaretogo opened this issue Jan 19, 2022 · 2 comments

Comments

@pietsoftwaretogo
Copy link

Hi,

I think I can best explain my issue with the following bash output.
My PC (running windows) is configured to be at UTC+01:00 and uses 24h clock instead of 12+AM/PM.
So the commit I want to include was 15:27 local time.

Running Gource v0.51

Any thoughts?

Also it would be really helpful in my use case if I could specify a start/end commit id instead of a specific date.
But it is probably not as easy as it sounds.

Thanks!

Piet@DESKTOP ~/source/repos/GourcePr (master)
$ gource --start-date "2022-01-15 14:00:00 +0"
gource: failed to generate log file for the specified time period
Try 'gource --help' for more information.


Piet@DESKTOP ~/source/repos/GourcePr (master)
$ git log
commit f0cdf550043f852c4396d560aca8b9cac8e5ab20 (HEAD -> master)
Author: Piet Eckhart <>
Date:   Sat Jan 15 14:27:51 2022 +0000

    ADD: Some IoC and range tweaks

commit 7b8a9d72ad67f4e92214efa24a41c70adb61e69e
Author: Piet Eckhart <>
Date:   Sat Jan 15 13:42:24 2022 +0000

    ADD: Gource time period
@acaudwell
Copy link
Owner

I tried to replicate the issue with a +0 timezone, but it seems to work. I wonder if there is a different issue with that commit.

You can make gource run using a log file. You can see the command it uses with gource --git-log-command. You could generate a log file and see if you still have the same issue with gource --start-date "2022-01-15 14:00:00 +0" logfile.txt. If its still not clear what the issue is you could attach it here and I can look at it.

@pieteckhart
Copy link

It prints out the following command:
git log --pretty=format:user:%aN%n%ct --reverse --raw --encoding=UTF-8 --no-renames --no-show-signature

when I execute it shows the correct commits with unix timestamps:

1642254144 Saturday, January 15, 2022 13:42:24
1642256871 Saturday, January 15, 2022 14:27:51

when i feed the output via logfile.txt it does seem to work. weird.

I think I'm going to use the logfile.txt approach for now. But if you like I could share my private repo if you would like to investigate some more. Thanks for the help so far :)

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

No branches or pull requests

3 participants