1. 24 May, 2012 3 commits
    • antirez's avatar
      BITOP: handle integer encoded objects correctly. · f0d962c0
      antirez authored
      A bug in the implementation caused BITOP to crash the server if at least
      one one of the source objects was integer encoded.
      
      The new implementation takes an additional array of Redis objects
      pointers and calls getDecodedObject() to get a reference to a string
      encoded object, and then uses decrRefCount() to release the object.
      
      Tests modified to cover the regression and improve coverage.
      f0d962c0
    • antirez's avatar
      Bit operations tests improved. · 951213e2
      antirez authored
      Fuzzing tests of BITCOUNT / BITOP are iterated multiple times.
      The new BITCOUNT fuzzing test uses random strings in a wider interval of
      lengths including zero-len strings.
      951213e2
    • antirez's avatar
      BITOP and BITCOUNT tests. · 1f40cdd0
      antirez authored
      The Redis implementation is tested against Tcl implementations of the
      same operation. Both fuzzing and testing of specific aspects of the
      commands behavior are performed.
      1f40cdd0
  2. 23 May, 2012 2 commits
    • antirez's avatar
      Redis test: include bug report on crash. · dfa90b59
      antirez authored
      Due to a change in the format of the bug report in case of crash of
      failed assertion the test suite was no longer able to properly log it.
      Instead just a protocol error was logged by the Redis TCL client that
      provided no clue about the actual problem.
      
      This commit resolves the issue by logging everything from the first line
      of the log including the string REDIS BUG REPORT, till the end of the
      file.
      dfa90b59
    • antirez's avatar
      Fixed issue #516 (ZINTERSTORE mixing sets and zsets). · 4dada1b5
      antirez authored
      Weeks ago trying to fix an harmless GCC warning I introduced a bug in
      the ziplist-encoded implementations of sorted sets.
      
      The bug completely broke zuiNext() iterator, that is used in the
      ZINTERSTORE and ZUNIONSTORE implementation, so those two commands are no
      longer reliable starting from Redis version 2.4.12 and latest 2.6.0-RC
      releases.
      
      This commit fixes the problem and adds a regression test.
      4dada1b5
  3. 12 May, 2012 1 commit
  4. 02 May, 2012 1 commit
  5. 30 Apr, 2012 2 commits
  6. 29 Apr, 2012 1 commit
  7. 27 Apr, 2012 2 commits
  8. 24 Apr, 2012 3 commits
  9. 21 Apr, 2012 1 commit
    • antirez's avatar
      Limit memory used by big SLOWLOG entries. · 590d55a2
      antirez authored
      Two limits are added:
      
      1) Up to SLOWLOG_ENTRY_MAX_ARGV arguments are logged.
      2) Up to SLOWLOG_ENTRY_MAX_STRING bytes per argument are logged.
      3) slowlog-max-len is set to 128 by default (was 1024).
      
      The number of remaining arguments / bytes is logged in the entry
      so that the user can understand better the nature of the logged command.
      590d55a2
  10. 19 Apr, 2012 1 commit
  11. 18 Apr, 2012 10 commits
  12. 17 Apr, 2012 2 commits
  13. 13 Apr, 2012 3 commits
  14. 10 Apr, 2012 1 commit
  15. 08 Apr, 2012 1 commit
  16. 07 Apr, 2012 4 commits
  17. 05 Apr, 2012 2 commits