On Wednesday, February 3, 2016 at 1:10:37 AM UTC-8, Niphlod wrote: > > it's like you execute a task in a request coming from a new user every > time. if you need to persist something, use a record in the db. >
I'm catching on to that. Trying to queue a task from a shell doesn't seem useful. The scheduler.queue_task() call succeeds, and scheduler.task_status() shows it as queued, but it never seems to execute, and if I exit the shell and pop over to the databases directory and invoke sqlite (this is not production, yet) it doesn't show in any scheduler tables. Going back to the shell, scheduler.task_status() doesn't show it anymore, and instead returns the entry for the last time the task was invoked by a real request. I was trying queuing the task from the shell as a way to experiment with conditional queuing. That is, on some event (like a real request), the models load, and we check to see if the task is queued, and if not do a new queue call. /dps > On Wednesday, February 3, 2016 at 7:24:07 AM UTC+1, Dave S wrote: >> >> >> >> On Sunday, January 31, 2016 at 4:13:07 AM UTC-8, Niphlod wrote: >>> >>> >>> >>> On Sunday, January 31, 2016 at 7:12:41 AM UTC+1, Dave S wrote: >>>> >>>> >>>> >>>> On Saturday, January 30, 2016 at 8:50:32 PM UTC-8, Niphlod wrote: >>>>> >>>>> scheduler_run is the only way to keep track of executions. >>>>> >>>> >>>> And there is no session to carry a value over in, is there? >>>> >>> >>> sorry, what ? >>> >> >> More precisely, there is a session, but it "expires" at the end of each >> run, so provides no persistance between runs. >> >> /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 [email protected]. For more options, visit https://groups.google.com/d/optout.
