- 10 Apr, 2014 1 commit
-
-
Matt Stancliff authored
Verify proper expire-before-delete behavior. This test passes with the expire-before-delete commit and fails without it.
-
- 03 Apr, 2014 1 commit
-
-
antirez authored
-
- 27 Feb, 2014 4 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
It was verified in practice that this test is able to stress much more the implementation by introducing errors that were only trivially to detect with different offsets but impossible to detect starting always at zero and counting bits the full length of the string.
-
- 13 Feb, 2014 1 commit
-
-
antirez authored
It was verified that reverting the commit that fixes the bug, the test no longer passes.
-
- 09 Jan, 2014 1 commit
-
-
antirez authored
-
- 08 Jan, 2014 1 commit
-
-
antirez authored
-
- 13 Dec, 2013 1 commit
-
- 08 Dec, 2013 1 commit
-
-
Yossi Gottlieb authored
-
- 25 Nov, 2013 1 commit
-
-
antirez authored
Fixes issue #1298.
-
- 05 Nov, 2013 1 commit
-
-
antirez authored
-
- 31 Oct, 2013 2 commits
- 30 Oct, 2013 6 commits
- 25 Oct, 2013 2 commits
-
-
antirez authored
-
Pieter Noordhuis authored
-
- 30 Aug, 2013 1 commit
-
-
antirez authored
-
- 29 Aug, 2013 1 commit
-
-
antirez authored
-
- 22 Jul, 2013 1 commit
-
-
antirez authored
-
- 19 Jun, 2013 1 commit
-
-
antirez authored
-
- 28 Mar, 2013 3 commits
- 27 Mar, 2013 2 commits
- 25 Mar, 2013 1 commit
-
-
antirez authored
Fixes #621.
-
- 12 Feb, 2013 2 commits
- 28 Jan, 2013 1 commit
-
-
antirez authored
-
- 21 Jan, 2013 1 commit
-
-
antirez authored
UNSUBSCRIBE and PUNSUBSCRIBE commands are designed to mass-unsubscribe the client respectively all the channels and patters if called without arguments. However when these functions are called without arguments, but there are no channels or patters we are subscribed to, the old behavior was to don't reply at all. This behavior is broken, as every command should always reply. Also it is possible that we are no longer subscribed to a channels but we are subscribed to patters or the other way around, and the client should be notified with the correct number of subscriptions. Also it is not pretty that sometimes we did not receive a reply at all in a redis-cli session from these commands, blocking redis-cli trying to read the reply. This fixes issue #714.
-
- 19 Jan, 2013 2 commits
- 15 Jan, 2013 1 commit
-
-
antirez authored
-