BTW: it has been merged . You can safely take scheduler.py from master and
overwrite your own if you want to avid specifying next_run_time
On Wednesday, September 21, 2016 at 5:57:44 PM UTC+2, Bernardo Leon wrote:
>
> Niphlod I will use postgresql in production and your solution as well.
>
Niphlod I will use postgresql in production and your solution as well.
Thank you for helping me! ;)
El miércoles, 21 de septiembre de 2016, 2:33:30 (UTC-5), Niphlod escribió:
>
> that error is due - mostly - when the backend is too much pressured (i.e.
> you're using sqlite, or too many
that error is due - mostly - when the backend is too much pressured (i.e.
you're using sqlite, or too many workers, or a too low heatbeat)
this is the fix https://github.com/web2py/web2py/pull/1453 . you can
subscribe to it to know when it'll be merged.
On Tuesday, September 20, 2016 at
Thank you for your reply. Can you reply this thread when the fix is
published?
I don't know if this is related to the same bug but in my worker process
terminal I have this message:
ERROR:web2py.scheduler.cedia-Satellite-L55-C#18606:error popping tasks
why do I have this error? Thanks.
sorry, a bug slipped in. In the wait for the fix, please use next_run_time
in addition to start_time.
On Monday, September 19, 2016 at 6:27:28 PM UTC+2, Bernardo Leon wrote:
>
> Hi, I am trying to run tasks in the future based on a time the user
> specifies but as soon as the task is queued it
5 matches
Mail list logo
