You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that when the last day of the month cron expression(59 23 L * *) is used, the getNextRunDate method skips March for some years and returns April instead. I was thinking this had to do with 2024 being a leap year, but when I ran test cases for other years, it turned out to not be only for leap years.
Failed asserting that two DateTime objects are equal.
Expected :2024-03-31T23:59:00.000000+0300Actual :2024-04-30T23:59:00.000000+0300Failed asserting that two DateTime objects are equal.
Expected :2019-03-31T23:59:00.000000+0300Actual :2019-04-30T23:59:00.000000+0300Failed asserting that two DateTime objects are equal.
Expected :2013-03-31T23:59:00.000000+0300Actual :2013-04-30T23:59:00.000000+0300Failed asserting that two DateTime objects are equal.
Expected :2002-03-31T23:59:00.000000+0300Actual :2002-04-30T23:59:00.000000+0300
So instead of returning last day of March, it returns last day of April for the years 2024, 2019, 2013 and 2002.
The text was updated successfully, but these errors were encountered:
I believe I have a fix for this, it is due to how time math was being handled. Before I release a fix, could I get your thoughts on #181 as it will impact the overall solution?
It seems that when the last day of the month cron expression(
59 23 L * *
) is used, thegetNextRunDate
method skips March for some years and returns April instead. I was thinking this had to do with 2024 being a leap year, but when I ran test cases for other years, it turned out to not be only for leap years.results in:
So instead of returning last day of March, it returns last day of April for the years 2024, 2019, 2013 and 2002.
The text was updated successfully, but these errors were encountered: