-
Notifications
You must be signed in to change notification settings - Fork 51
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
Doesn't work with Commits after Jan 1, 2020 #23
Comments
Ugh... Looked at the code and it does not seem to be any particular reason to not have upper bound calculated from current date (may a day in a future to cover and possible time zones diffs). |
AndreyNikiforov
changed the title
Doesn't work with Commits after Jan 1, 2010
Doesn't work with Commits after Jan 1, 2020
Feb 23, 2020
That would work... or you can just use something really far in the future
(like 2120).
BTW, it is an amazing tool and I really enjoyed using it.
…On Sun, Feb 23, 2020 at 7:07 PM Andrey Nikiforov ***@***.***> wrote:
Ugh... Looked at the code and it does not seem to be any particular reason
to not have upper bound calculated from current date (may a day in a future
to cover and possible time zones diffs).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#23?email_source=notifications&email_token=AB4MTB4UEHBTNVKFKRZRX5DREKUNFA5CNFSM4KZT74L2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMWBK6Q#issuecomment-590091642>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB4MTB4IB3CNZPJWPWY2MELREKUNFANCNFSM4KZT74LQ>
.
|
@davidasconsulting do you happen to have a fix that you can submit as PR? |
I submitted a PR |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Processor.cs, line 296, the time range is from 2000 - Jan 1, 2020 so all commits after that don't work.
Update the line to a later date and all will be fine
The text was updated successfully, but these errors were encountered: