This repository has been archived by the owner on Jan 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 170
timezone related error on DST on Next() #23
Comments
It's fixed in PR #17 |
thanks, could you make it public so I can test it,
…On Fri, Dec 9, 2016 at 6:52 PM, Augusto Becciu ***@***.***> wrote:
It's fixed in PR #17 <#17>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH_TmSG9LDO19pu1dEdvjOL3iTc_ATTFks5rGhP1gaJpZM4LJf0k>
.
|
It's public, just pull the branch into your repo. |
Thanks that I am doing now. will u still plan to merge to master?
…On Tue, Dec 13, 2016 at 10:11 AM Augusto Becciu ***@***.***> wrote:
It's public, just pull the branch into your repo.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AH_TmaVKhVNw5X4Rfr5IfcEK4SEqJUKtks5rHt_rgaJpZM4LJf0k>
.
|
on this commit, I found a new error. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
step to reproduce:
1.get first schedule time
schedule= 2 02 * * * *
fromTime=2016-03-12 02:03:00 -0800 PST
call Next() return: 2016-03-13T01:02:00-08:00
2. get next schedule time.
use the Next() return time as new fromTime: 2016-03-13T01:02:00-08:00
call Next() again ,and return the same value as new fromTime: 2016-03-13T01:02:00-08:00
The text was updated successfully, but these errors were encountered: