Sascha Roland c1e9186f06 #5299 Fix blocking XREAD for streams that ran dry
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.
2018-09-04 13:13:36 +02:00
..
2018-07-03 18:19:46 +02:00
2012-04-13 17:52:33 -07:00
2016-04-25 16:49:57 +03:00
2016-06-07 16:46:00 -04:00
2018-07-04 20:04:06 +08:00
2018-03-21 15:34:13 +08:00
2016-04-04 08:50:58 +02:00
2018-07-03 18:19:46 +02:00
2015-10-01 13:02:25 +02:00
2018-07-03 18:19:46 +02:00
2018-07-03 18:19:46 +02:00
2018-07-18 10:16:33 +03:00
2018-07-17 10:39:47 +02:00
2017-12-05 15:38:03 +01:00
2018-07-03 18:19:46 +02:00
2018-06-21 22:08:09 +08:00
2018-07-03 18:19:46 +02:00
2018-06-12 15:28:28 +08:00
2016-07-27 11:34:25 +02:00
2018-06-27 16:33:31 +03:00
2018-07-03 18:19:46 +02:00
2018-07-03 18:19:46 +02:00
2018-07-13 09:46:30 -06:00
2018-07-30 16:18:56 +03:00
2018-07-03 18:19:46 +02:00
2014-08-08 10:05:32 +02:00
2018-07-03 18:19:46 +02:00
2018-07-03 18:19:46 +02:00
2018-07-03 18:19:46 +02:00
2018-07-12 21:21:37 +08:00
2018-07-03 18:19:46 +02:00
2015-04-27 12:07:49 +02:00
2015-04-27 12:07:49 +02:00
2018-07-03 18:19:46 +02:00
2014-07-02 16:31:22 +02:00
2018-07-31 16:41:33 +02:00
2018-08-01 19:04:53 +02:00
2018-07-24 10:27:20 +02:00
2017-01-11 19:24:19 +02:00
2011-07-06 15:22:00 +02:00
2018-07-03 18:19:46 +02:00
2018-07-22 10:17:35 +03:00