Putting the clock forwards causes cron to catch-up and run multiple times about cron HOT 8 CLOSED

I think that the reason I used 'effective' instead of 'now' is to avoid missing jobs in case of random pauses. I agree that your use case seems pretty motivating to adjust things. All of the tests pass when I make the change you describe, so at least I doesn't break anything in the typical case.

Want to give it a shot and report back how it goes?

from cron.

Yeah will do. I have tested messing around with the clock and everything works fine with the change. Normal behaviour seems ok so I think it will be fine. I will report back in few weeks and let you know how it goes.

from cron.

Hi @robfig, thought I'd report back.

I've been using my patch now in production for few days and this has solved my problems and doesn't seem to have had any regression effects. Should we push this fix to master?

from cron.

Good to hear! My only concern is the behavior during daylight savings transitions. I'm not sure how to test that though..

from cron.

Is this fix currently under consideration for v2?

from cron.

Sure, I'm happy to merge it

from cron.

Lovely! :)

from cron.

I believe this was merged and all good. Closing

from cron.