Re: [Twisted-Python] LoopingCall.withCount countCallable called with 0

Thank you glyph and moshez for working on this! 2015-05-09 22:04 GMT+02:00 Glyph : > > On Mar 26, 2015, at 2:06 AM, Dario Vinella wrote: > > Here it is a log where I print a dot when the calls arg is 1, the value if > not 1, each dot is separated by 0.02s > > https://gist.github.com/dvinella/73e

Re: [Twisted-Python] LoopingCall.withCount countCallable called with 0

> On Mar 26, 2015, at 2:06 AM, Dario Vinella wrote: > > Here it is a log where I print a dot when the calls arg is 1, the value if > not 1, each dot is separated by 0.02s > > https://gist.github.com/dvinella/73e5e45a04c428f037bf > > >

Re: [Twisted-Python] LoopingCall.withCount countCallable called with 0

2015-03-24 23:18 GMT+01:00 Glyph Lefkowitz : > It would be good to look at how many of these numbers are negative. > Not a single one, running the script for a couple of hours, under any condition > > That seems right. I think there's a real problem here, since physical > clocks do just fail,

Re: [Twisted-Python] LoopingCall.withCount countCallable called with 0

> On Mar 24, 2015, at 2:49 AM, Dario Vinella wrote: > > Hi all, > > I found an odd behavior using a LoopingCall.withCount with a very small > interval (0.02 sec): sometimes the countCallable is called with 0 as argument > and it looks like the now - _realLastTime is smaller than the looping

[Twisted-Python] LoopingCall.withCount countCallable called with 0

Hi all, I found an odd behavior using a LoopingCall.withCount with a very small interval (0.02 sec): sometimes the countCallable is called with 0 as argument and it looks like the now - _realLastTime is smaller than the looping interval. Here you can find the very simple code I use to reproduce t