Related, but not exactly the same question: I'm submitting an immediate task in a regular (no sleep or anything -- though no special commit either); I can see it's queued for seconds and sometimes minutes before getting assigned and running.
There are no other tasks waiting or running, there are one or two schedulers running (one starts with app server, one independently - but I tried only one with same results). Before I dig deep into debugging the scehduler - is there something simple I might be missing? Other things: main app db, auth db and sched db are all different, and all are SQLite files. Running on Linux. Tasks are given a uuid by me (easiest way to track if something was done in a previous run or not - uuid reflects the exact operation needed). Thanks in advance. On Friday, November 28, 2014 7:30:44 PM UTC+2, Niphlod wrote: > > def test(): > newid = sched.queue_task(...., immediate=True) > db.commit() #the db instance where the scheduler is > while True: > rtn = sched.task_status(newid) > if rtn.status == 'COMPLETED': > ...blablabla > break > time.sleep(3) > > > not tested (haven't a web2py to try it on ATM) but you get the idea.... > > On Friday, November 28, 2014 7:30:18 AM UTC+1, Manuele wrote: >> >> Hi, >> I would like to add an immediate task to the scheduler and wait for the >> result within the same submit. Is it possible? How? >> >> Thank you very mutch >> >> Manuele >> > -- 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.
