- 13 Nov, 2019 1 commit
-
-
Guy Benoish authored
Calling XADD with 0-0 or 0 would result in creating an empty key and storing it in the database. Even worse, because XADD will reply with error the action will not be replicated, creating a master-replica inconsistency
-
- 04 Nov, 2019 1 commit
-
-
Loris Cro authored
-
- 10 Oct, 2019 1 commit
-
-
Guy Benoish authored
-
- 11 Apr, 2019 1 commit
-
-
James Rouzier authored
-
- 12 Mar, 2019 1 commit
-
-
Steve Webster authored
-
- 08 Mar, 2019 1 commit
-
-
Steve Webster authored
The XCLAIM docs state the XCLAIM increments the delivery counter for messages. This PR makes the code match the documentation - which seems like the desired behaviour - whilst still allowing RETRYCOUNT to be specified manually. My understanding of the way streamPropagateXCLAIM() works is that this change will safely propagate to replicas since retry count is pulled directly from the streamNACK struct. Fixes #5194
-
- 16 Jan, 2019 1 commit
-
-
zhaozhao.zz authored
Fix issue #5785, in case create group on a key is not stream.
-
- 09 Jan, 2019 1 commit
-
-
antirez authored
-
- 19 Nov, 2018 3 commits
-
-
antirez authored
This commit fixes #5570. It is a similar bug to one fixed a few weeks ago and is due to the range API to be called with NULL as "end ID" parameter instead of repeating again the start ID, to be sure that we selectively issue the entry with a given ID, or we get zero returned (and we know we should emit a NULL reply).
-
antirez authored
This fixes the issue reported in #5570. This was fixed the hard way, that is, propagating more information to the lower level API about this being a request to read just the history, so that the code is simpler and less likely to regress.
-
antirez authored
-
- 05 Nov, 2018 2 commits
-
-
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.
-
antirez authored
-
- 03 Nov, 2018 1 commit
-
-
michael-grunder authored
This fixes an overflow on 32-bit systems.
-
- 31 Oct, 2018 1 commit
-
-
Guy Korland authored
-
- 25 Oct, 2018 2 commits
- 24 Oct, 2018 1 commit
-
-
antirez authored
-
- 17 Oct, 2018 7 commits
-
-
Itamar Haber authored
-
antirez authored
They play better with Lua scripting, otherwise Lua will see status replies as "ok" = "string" which is very odd, and actually as @oranagra reasoned in issue #5456 in the rest of the Redis code base there was no such concern as saving a few bytes when the protocol is emitted.
-
Itamar Haber authored
-
antirez authored
-
antirez authored
-
antirez authored
This avoids issues with having to replicate a command that produced errors.
-
antirez authored
-
- 16 Oct, 2018 2 commits
- 15 Oct, 2018 3 commits
- 11 Oct, 2018 4 commits
-
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
Because the NACK->consumer is NULL, if idletime < minidle the NACK does not belong to any consumer, then redis will crash in XPENDING.
-
zhaozhao.zz authored
-
- 10 Oct, 2018 1 commit
-
-
antirez authored
Issue #5433.
-
- 09 Oct, 2018 2 commits
-
-
zhaozhao.zz authored
-
zhaozhao.zz authored
XSTREAM CREATE <key> <id or *> -- Create a new empty stream. XSTREAM SETID <key> <id or $> -- Set the current stream ID.
-
- 08 Oct, 2018 1 commit
-
-
antirez authored
See #5141.
-
- 04 Oct, 2018 1 commit
-
-
antirez authored
-
- 02 Oct, 2018 1 commit
-
-
antirez authored
-