1. 21 Jun, 2014 14 commits
  2. 09 Jun, 2014 1 commit
    • Matt Stancliff's avatar
      Fix blocking operations from missing new lists · 7fc1fc8c
      Matt Stancliff authored
      Behrad Zari discovered [1] and Josiah reported [2]: if you block
      and wait for a list to exist, but the list creates from
      a non-push command, the blocked client never gets notified.
      
      This commit adds notification of blocked clients into
      the DB layer and away from individual commands.
      
      Lists can be created by [LR]PUSH, SORT..STORE, RENAME, MOVE,
      and RESTORE.  Previously, blocked client notifications were
      only triggered by [LR]PUSH.  Your client would never get
      notified if a list were created by SORT..STORE or RENAME or
      a RESTORE, etc.
      
      Blocked client notification now happens in one unified place:
        - dbAdd() triggers notification when adding a list to the DB
      
      Two new tests are added that fail prior to this commit.
      
      All test pass.
      
      Fixes #1668
      
      [1]: https://groups.google.com/forum/#!topic/redis-db/k4oWfMkN1NU
      [2]: #1668
      7fc1fc8c
  3. 06 Jun, 2014 1 commit
  4. 05 Jun, 2014 1 commit
  5. 04 Jun, 2014 1 commit
  6. 26 May, 2014 3 commits
  7. 23 May, 2014 5 commits
  8. 20 May, 2014 8 commits
  9. 19 May, 2014 1 commit
  10. 07 May, 2014 2 commits
    • antirez's avatar
      Scripting test: check that Lua can call commands rewirting argv. · 35b94422
      antirez authored
      SPOP, tested in the new test, is among the commands rewritng the
      client->argv argument vector (it gets rewritten as SREM) for command
      replication purposes.
      
      Because of recent optimizations to client->argv caching in the context
      of the Lua internal Redis client, it is important to test for SPOP to be
      callable from Lua without bad effects to the other commands.
      35b94422
    • antirez's avatar
      Test: handle new osx 'leaks' error. · 1255460c
      antirez authored
      Sometimes the process is still there but no longer in a state that can
      be checked (after being killed). This used to happen after a call to
      SHUTDOWN NOSAVE in the scripting unit, causing a false positive.
      1255460c
  11. 05 May, 2014 3 commits