Thanks for the great work on the scheduler niphlod! On Wednesday, August 1, 2012 1:19:48 PM UTC-7, Niphlod wrote: > > The consideration behind that is that if your function doesn't return > anything, you don't need the results. Backward compatibility is quite > broken in that sense (but scheduler is still marked as experimental). > If the function returns something, the scheduler_run record is preserved > (unless the discard_results parameter is set to True). > We thought that if for some strange reason a user still needs the > scheduler_run record, he could easily add a "return 1" at the end and the > behaviour of the "old" scheduler is preserved. > Traceback are always saved (no matter what). > > > On Wednesday, August 1, 2012 9:56:55 PM UTC+2, Vincenzo Ampolo wrote: >> >> On 08/01/2012 12:49 PM, Niphlod wrote: >> > Happy to see someone noticing actual improvements :P >> > If you need any further explanations / tips&tricks, just ask. >> > >> > PS: another italian added to web2py-users ;) >> >> Thanks :) >> >> just some considerations though. >> >> I noticed that now in scheduler_run all the COMPLETED tasks get >> cancelled. >> Will it happen even if the completed one have an output? >> >> If there is a FAILED am I going to see the traceback from the >> scheduler_task -> scheduler_run relation like I was doing before? >> >> btw went up to 14 workers. only 3.00 load :) woot woot (that means that >> the overall scheduling system is *really* lighweight) >> >> -- >> Vincenzo Ampolo >> http://vincenzo-ampolo.net >> http://goshawknest.wordpress.com >> >
--
