2016-10-17 21:11 GMT+02:00 Niphlod :
> BTW: please start adapting your code to use mysched.queue_task()
> instead of db.scheduler_task.insert(...) .
> Next releases could change the format of the scheduler_task table and only
> the queue_task method is the supported one
It works perfect - thank you!
2016-10-17 21:08 GMT+02:00 Niphlod :
> the bug has already been fixed in trunk.
> You can copy/paste the scheduler.py file from master if you want it
> solved, or either pass next_run_time equal to start_time to make things
> work the way they
BTW: please start adapting your code to use mysched.queue_task()
instead of db.scheduler_task.insert(...) .
Next releases could change the format of the scheduler_task table and only
the queue_task method is the supported one (i.e. will handle eventual
corner-cases that won't be possible
the bug has already been fixed in trunk.
You can copy/paste the scheduler.py file from master if you want it solved,
or either pass next_run_time equal to start_time to make things work the
way they were.
On Sunday, October 16, 2016 at 8:30:23 AM UTC+2, mweissen wrote:
>
> Thank you, but
Thank you, but start_time has a value.
start_time is a paramter of the surrounding function.
I have tested it with
task_name = task_name + str(start_time)
and therefore I have written start_time != None
2016-10-15 19:59 GMT+02:00 Dave S :
>
>
> On Saturday, October 15,
On Saturday, October 15, 2016 at 6:27:33 AM UTC-7, mweissen wrote:
>
> It seems that the start_time parameter in a scheduler_task record does not
> work correctly.
>
> For example:
>
> I add a record to scheduler_task which should start the function
> "smsEmailAussenden" (means "send the
6 matches
Mail list logo