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