Open TsimafeiTsykunou opened 4 years ago
@Eugeny could you help with it, please?
No, sorry, I'm not one of the core developers.
Guys?? Does anyone supporting this package??
@Eugeny Hi again. I actually found out that the issue is in get_next_sheduled_time method: it calculates cron next scheduled time relative to current time and so if job was enqued 2020-01-01 3:00:00AM it will be scheduled again to 2020-01-01 3:00AM because cron_string not using seconds but now var using it.
now
isn't "using" seconds, it's a datetime
object.
@Eugeny datetime.utcnow()
returns whole time with seconds.
Hello? Could anyone assist with this issue?? Almost 3 weeks have passed since the opening...
@TsimafeiTsykunou please open a PR for this :)
Found weird behaviour, when you specify cronstring like
0 3 * * *
job will be executed 2 times: 1) at 3:00 2) at 3:01