[web2py] Re: Bug in gluon/scheduler.py

2022-08-19 Thread Dave S
On Monday, August 8, 2022 at 3:50:26 AM UTC-7 Tom Clerckx wrote: > Version: > Version 2.22.5-stable+timestamp.2022.06.04.18.13.51 > > There is a problem with the calculation of next_run_time in > gluon/scheduler.py at line 1024 > > It calculates: > steps = secondspassed // task.period + 1 > > H

[web2py] Re: Bug in gluon/scheduler.py

2022-08-20 Thread Tom Clerckx
Our tasks are added using scheduler.queue_task(...) function. By default, we set the period to 0 Later on we added to the defaults : prevent_drift = True It's this last change that triggered the observed error. On Friday, August 19, 2022 at 12:49:05 PM UTC+2 snide...@gmail.com wrote: > O

[web2py] Re: Bug in gluon/scheduler.py

2022-08-21 Thread Dave S
On Saturday, August 20, 2022 at 11:39:55 AM UTC-7 Tom Clerckx wrote: > Our tasks are added using scheduler.queue_task(...) function. > > By default, we set the period to 0 > Why? If you don't know the period, why are you queuing it? Or are you using the "cron" type of task scheduling?