- 25 Jan, 2016 1 commit
-
-
antirez authored
-
- 08 Jan, 2016 1 commit
-
-
antirez authored
This fix, provided by Paul Kulchenko (@pkulchenko), allows the Lua scripting engine to evaluate statements with a trailing comment like the following one: EVAL "print() --comment" 0 Lua can't parse the above if the string does not end with a newline, so now a final newline is always added automatically. This does not change the SHA1 of scripts since the SHA1 is computed on the body we pass to EVAL, without the other code we add to register the function. Close #2951.
-
- 02 Jan, 2016 1 commit
-
-
antirez authored
-
- 18 Dec, 2015 1 commit
-
-
antirez authored
-
- 17 Dec, 2015 1 commit
-
-
antirez authored
It's a key invariant that when AOF is enabled, after the cluster reshards, a crash-recovery event causes all the keys to be still fine with the expected logical content. Now this is part of unit 04.
-
- 13 Dec, 2015 2 commits
- 10 Dec, 2015 2 commits
-
-
antirez authored
The old version was modeled with two failovers, however after the first it is possible that another slave will migrate to the new master, since for some time the new master is not backed by any slave. Probably there should be some pause after a failover, before the migration. Anyway the test is simpler in this way, and depends less on timing.
-
antirez authored
-
- 15 Oct, 2015 1 commit
-
-
antirez authored
-
- 15 Sep, 2015 1 commit
-
-
antirez authored
HINCRBY* tests later used the value "tmp" that was sometimes generated by the random key generation function. The result was ovewriting what Tcl expected to be inside Redis with another value, causing the next HSTRLEN test to fail.
-
- 14 Sep, 2015 2 commits
-
-
antirez authored
Related to #2765.
-
antirez authored
MOVE was not able to move the TTL: when a key was moved into a different database number, it became persistent like if PERSIST was used. In some incredible way (I guess almost nobody uses Redis MOVE) this bug remained unnoticed inside Redis internals for many years. Finally Andy Grunwald discovered it and opened an issue. This commit fixes the bug and adds a regression test. Close #2765.
-
- 05 Aug, 2015 4 commits
- 29 May, 2015 3 commits
- 19 May, 2015 1 commit
-
-
antirez authored
-
- 15 May, 2015 1 commit
-
-
Glenn Nethercutt authored
uphold the smove contract to return 0 when the element is not a member of the source set, even if source=dest
-
- 01 Apr, 2015 1 commit
-
-
antirez authored
This should likely fix a false positive when running with the --valgrind option.
-
- 30 Mar, 2015 1 commit
-
-
antirez authored
-
- 27 Mar, 2015 1 commit
-
-
antirez authored
-
- 22 Mar, 2015 4 commits
- 18 Mar, 2015 1 commit
-
-
antirez authored
-
- 10 Feb, 2015 2 commits
-
-
antirez authored
This test on Linux was extremely slow, since in Tcl we can't enable easily tcp-nodelay, so the busy loop used to take *a lot* with bigger writes. Fixed using pipelining.
-
antirez authored
This test on Linux was extremely slow, since in Tcl we can't enable easily tcp-nodelay, so the busy loop used to take *a lot* with bigger writes. Fixed using pipelining.
-
- 22 Jan, 2015 8 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
Removes some percentage of timing related failures.
-
antirez authored
Otherwise between the two commands other nodes may contact us making the next SET-CONFIG-EPOCH call impossible.
-
antirez authored
Otherwise kill_instance + restart_instance in short succession will still find the port busy and will fail.
-
antirez authored
-
antirez authored
-
Matt Stancliff authored
-