[web2py] Re: Scheduler timing out even though the task completes

you're the third one reporting those strange issues but for the life of me I can't seem to find a reference for this specific "weirdness" and/or a fix for it. Anyway I'm happy to have pinpointed the root cause On Tuesday, November 24, 2015 at 7:42:05 PM UTC+1, Benson Myrtil wrote: > > We are loo

[web2py] Re: Scheduler timing out even though the task completes

We are looking good. THANKS!!! Had a lot of stuff printing to the console. Removed those print statements and the task appears to be completing successfully now with no timeout issues so far. Thanks a lot!!! On Monday, November 23, 2015 at 4:40:35 PM UTC-5, Niphlod wrote: > > If you're really

[web2py] Re: Scheduler timing out even though the task completes

If you're really returning at the end (not near, the actual end) how many records were added, the very "returned" data would cause your task to be COMPLETED. If you're printing near the end, and then returning something, then the task TIMEOUTing is probably stuck trying to flush stdout/stderr b