Then a day later I saw Redis commands getting interleaved because Ruby's Timeout is inherently unsafe...
-
-
Replying to @bascule
@bascule@nahi had the same issue going from 1.9 to 2.1. After a timeout occurs redis return values are off by 1+https://gist.github.com/stevehodgkiss/10204388 …2 replies 1 retweet 3 likes -
Replying to @stevehodgkiss
@stevehodgkiss@bascule@nahi is this due to Ruby timeouts or a bug? Looks more like it should reconnect after timeout but does not.2 replies 0 retweets 0 likes -
Replying to @antirez
@antirez@bascule@nahi I agree, it sounds more like a bug in redis-rb. Here’s the issue I opened at the time:https://github.com/redis/redis-rb/issues/424 …1 reply 0 retweets 2 likes -
Replying to @stevehodgkiss
@stevehodgkiss@antirez@nahi we have a simpler repro for this that even works against the hiredis backend1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@nahi@stevehodgkiss would be great to have a repro posted in the redis-rb repo if possible. Thanks!2 replies 0 retweets 1 like
@antirez @nahi @stevehodgkiss will do
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.