Closed marshhj closed 7 years ago
Thank you very much for pointing this one out.
Fixed in version 1.2.1
Thanks for fixing! But the bug still exists........ And the fix bring new bugs.....
I'll look again into this today.
Okay, you're completely right - thank you again. The getNext() calculation was flawed when crossing month boundaries. I admit there should be more unit tests for that particular method.
The error should be fixed in current master branch. Would you be so kind and do a test? I also added another unit test for when "1 0 *" goes into next month.
Fixed in version 1.2.2
if Cron('1 0 *'), getNext() will return next day 00:00:00 ? why not 00:01:00 ???