1. 06 Mar, 2013 6 commits
  2. 04 Mar, 2013 4 commits
  3. 12 Feb, 2013 3 commits
  4. 11 Feb, 2013 9 commits
  5. 08 Feb, 2013 1 commit
  6. 07 Feb, 2013 1 commit
  7. 05 Feb, 2013 7 commits
  8. 04 Feb, 2013 2 commits
  9. 23 Jan, 2013 1 commit
  10. 21 Jan, 2013 4 commits
    • antirez's avatar
      bfad381f
    • antirez's avatar
      UNSUBSCRIBE and PUNSUBSCRIBE: always provide a reply. · 742e580f
      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.
      742e580f
    • antirez's avatar
      Fixed a bug in memtest progress bar, that had no actual effects. · 1b0f2445
      antirez authored
      This closes issue #859, thanks to @erbenmo.
      1b0f2445
    • antirez's avatar
      Not every __sun has backtrace(). · 580f65a5
      antirez authored
      I don't know how to test for Open Solaris that has support for
      backtrace() so for now removing the #ifdef that breaks compilation under
      other Solaris flavors.
      580f65a5
  11. 19 Jan, 2013 2 commits
    • antirez's avatar
      Additionally two typos fixed thanks to @jodal · a154908a
      antirez authored
      a154908a
    • antirez's avatar
      Whitelist SIGUSR1 to avoid auto-triggering errors. · da540228
      antirez authored
      This commit fixes issue #875 that was caused by the following events:
      
      1) There is an active child doing BGSAVE.
      2) flushall is called (or any other condition that makes Redis killing
      the saving child process).
      3) An error is sensed by Redis as the child exited with an error (killed
      by a singal), that stops accepting write commands until a BGSAVE happens
      to be executed with success.
      
      Whitelisting SIGUSR1 and making sure Redis always uses this signal in
      order to kill its own children fixes the issue.
      da540228