Re: [web2py] Re: web2py scheduler with huge output or return values always timeout (even if the task finishes)

2016-02-29 Thread Boris Aramis Aguilar Rodríguez
It happends not only while printing but also when returning values on a function as noted on the example :) so yes i do avoid printing but this also happens when returning more than 128kb of data (as noted by the bug reports) due to the fact (it seems) that the max data a process can comunicate to

Re: [web2py] Re: web2py scheduler with huge output or return values always timeout (even if the task finishes)

2016-02-29 Thread Niphlod
uhm, not sure about that though. the order of operations in the scheduler respects the docs, and even if the bugreport has the 128k statement, the docs don't report it let me try. On Monday, February 29, 2016 at 9:14:41 PM UTC+1, Boris Aramis Aguilar Rodríguez wrote: > > It happends not

Re: [web2py] Re: web2py scheduler with huge output or return values always timeout (even if the task finishes)

2016-02-29 Thread Boris Aramis Aguilar Rodríguez
Please do try :) I might be wrong :P and it could be something else; but I tried to narrow it down as much as I could. El feb 29, 2016 2:26 PM, "Niphlod" escribió: > uhm, not sure about that though. the order of operations in the scheduler > respects the docs, and even if the bugreport has the 12

Re: [web2py] Re: web2py scheduler with huge output or return values always timeout (even if the task finishes)

2016-02-29 Thread Niphlod
aw hell, it's true. huge outputs are effectively blocking. don't know if it's fixable though. I don't see any obvious error in the implementation that could prevent it On Monday, February 29, 2016 at 9:26:38 PM UTC+1, Niphlod wrote: > > uhm, not sure about that though. the order of opera