Thanks Niphlod. The scheduler really is a most excellent thing to use. On Sunday, August 25, 2013 12:07:09 AM UTC+12, Niphlod wrote: > > Thanks for spotting this. Scheduler global variables are safe in the > scheduler module, but inside the function that creates the environment to > run the task, they may got overwritten, causing problems. I sent a PR on > github to fix the issue. > > On Saturday, August 10, 2013 12:03:10 AM UTC+2, Limedrop wrote: >> >> Hi, >> >> I was experiencing some strange results with the scheduler in one >> particular application. Tasks would successfully execute, but the >> scheduler_task and scheduler_run records would stick on RUNNING. >> >> After some hair pulling I discovered that the app model was using this >> variable: >> >> COMPLETED = 'Completed' >> >> And so task_report.status was being set as 'Completed' whereas >> scheduler.py expects: >> >> COMPLETED = 'COMPLETED' >> >> So "if task_report.status == COMPLETED" could never be True. >> >> Is this just something to work around or is it possible to make scheduler >> play more nicely with the app namespace? >> >> Thanks >> >> >> >> >> >>
-- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
