1. 09 Jan, 2019 1 commit
  2. 19 Nov, 2018 3 commits
  3. 05 Nov, 2018 2 commits
    • antirez's avatar
      Fix XCLAIM missing entry bug. · 6ba50784
      antirez authored
      This bug had a double effect:
      
      1. Sometimes entries may not be emitted, producing broken protocol where
      the array length was greater than the emitted entires, blocking the
      client waiting for more data.
      
      2. Some other time the right entry was claimed, but a wrong entry was
      returned to the client.
      
      This fix should correct both the instances.
      6ba50784
    • antirez's avatar
      Improve streamReplyWithRange() top comment. · e7c579e1
      antirez authored
      e7c579e1
  4. 03 Nov, 2018 1 commit
  5. 31 Oct, 2018 1 commit
  6. 25 Oct, 2018 2 commits
  7. 24 Oct, 2018 1 commit
  8. 17 Oct, 2018 7 commits
  9. 16 Oct, 2018 2 commits
  10. 15 Oct, 2018 3 commits
  11. 11 Oct, 2018 4 commits
  12. 10 Oct, 2018 1 commit
  13. 09 Oct, 2018 2 commits
  14. 08 Oct, 2018 1 commit
  15. 04 Oct, 2018 1 commit
  16. 02 Oct, 2018 2 commits
  17. 01 Oct, 2018 1 commit
  18. 20 Sep, 2018 1 commit
  19. 04 Sep, 2018 1 commit
    • Sascha Roland's avatar
      #5299 Fix blocking XREAD for streams that ran dry · c1e9186f
      Sascha Roland authored
      The conclusion, that a xread request can be answered syncronously in
      case that the stream's last_id is larger than the passed last-received-id
      parameter, assumes, that there must be entries present, which could be
      returned immediately.
      This assumption fails for empty streams that actually contained some
      entries which got removed by xdel, ... .
      
      As result, the client is answered synchronously with an empty result,
      instead of blocking for new entries to arrive.
      An additional check for a non-empty stream is required.
      c1e9186f
  20. 03 Aug, 2018 2 commits
  21. 01 Aug, 2018 1 commit