1. 31 Oct, 2018 1 commit
  2. 25 Oct, 2018 2 commits
  3. 24 Oct, 2018 1 commit
  4. 17 Oct, 2018 7 commits
  5. 16 Oct, 2018 2 commits
  6. 15 Oct, 2018 3 commits
  7. 11 Oct, 2018 4 commits
  8. 10 Oct, 2018 1 commit
  9. 09 Oct, 2018 2 commits
  10. 08 Oct, 2018 1 commit
  11. 04 Oct, 2018 1 commit
  12. 02 Oct, 2018 2 commits
  13. 01 Oct, 2018 1 commit
  14. 20 Sep, 2018 1 commit
  15. 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
  16. 03 Aug, 2018 2 commits
  17. 01 Aug, 2018 4 commits
  18. 31 Jul, 2018 1 commit
  19. 30 Jul, 2018 2 commits
  20. 24 Jul, 2018 1 commit