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 From 2.1 it broke (off by 1? can I see backtrace?) but works in 1.9 without problem, right? The change looks safe...1 reply 0 retweets 0 likes -
Replying to @nahi
@nahi@stevehodgkiss the repro I have (will try to post it publicly tomorrow) is broken on 2.1.5 but works on 2.01 reply 0 retweets 0 likes
@nahi @stevehodgkiss we were seeing an exception silently swallowed before the response was consumed, so next req saw prev response
1:29 PM - 19 Jan 2015
0 replies
0 retweets
0 likes
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.