On Monday, November 12, 2018 at 1:09:22 PM UTC-8, Dave S wrote: > > > > On Friday, November 9, 2018 at 5:51:48 PM UTC-8, Dave S wrote: >> >> I'm trying to add a second scheduler item of work. At the moment, I seem >> to get the scheduler to run the new function some of the time, and to be >> stuck in the cue other times. >> > [...]
> Meanwhile, the original function is being picked up at the time it's >> queued for., and task_worker.last_heartbeat is ticking. >> >> Does anyone see why these are stuck? >> > > > Evidently repeats=0 is wrong even for a one-shot task. I changed it > repeats=1, and the task now gets changed to COMPLETED, but nothing shows > for that task in scheduler_run. I think the function is erroring out, > but there's no stack trace in scheduler_run, and nothing in errors/* > either. > > Oh, yeah, the function needs to return something to be in scheduler_run (requirement masked by tracebacks being a kind of return). > (I know I jumped the code into the scheduler before it was ready, but for > some reason when I tried running code in a shell, the -S myapp -M wasn't > giving me access to db().) > > /dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
