View Single Post
Posts: 123 | Thanked: 33 times | Joined on Jan 2010 @ Stockholm
#131
Originally Posted by lorelei View Post
There's a chance in 60 (very exactly!) that you will get this bug: in fact it is triggered when the timestamp of the last update falls exactly at a whole minute (for instance 12:30:00).
So, adding a second to the timestamp in config would have solved it? Anyway, 0.1.2 did.
/P