- 10 May, 2019 1 commit
-
-
zhaozhao.zz authored
-
- 26 Apr, 2019 4 commits
-
-
David Carlier authored
-
yongman authored
-
James Rouzier authored
-
Salvatore Sanfilippo authored
removed obsolete warning as per - https://github.com/antirez/redis/is…
-
- 25 Apr, 2019 1 commit
-
-
- 10 Apr, 2019 2 commits
-
-
antirez authored
-
Oran Agra authored
when redis appends the blocked client reply list to the real client, it didn't bother to check if it is in fact the master client. so a slave executing that module command will send replies to the master, causing the master to send the slave error responses, which will mess up the replication offset (slave will advance it's replication offset, and the master does not)
-
- 18 Mar, 2019 9 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
John Sully authored
-
Brad Solomon authored
On `make uninstall`, removes: - /usr/local/bin/redis-benchmark - /usr/local/bin/redis-check-aof - /usr/local/bin/redis-check-rdb - /usr/local/bin/redis-cli - /usr/local/bin/redis-sentinel - /usr/local/bin/redis-server (Only the src/ versions are removed in `make clean`)
-
antirez authored
Bug signaled by @vattezhang in PR #5940 but fixed differently.
-
- 14 Mar, 2019 17 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
Guy Benoish authored
In some cases processMultibulkBuffer uses sdsMakeRoomFor to expand the querybuf, but later in some cases it uses that query buffer as is for an argv element (see "Optimization"), which means that the sds in argv may have a lot of wasted space, and then in case modules keep that argv RedisString inside their data structure, this space waste will remain for long (until restarted from rdb).
-
Guy Benoish authored
-
Guy Benoish authored
-
Guy Benoish authored
-
Guy Benoish authored
The string representation of `long double` may take up to ~5000 chars (see PR #3745). Before this fix HINCRBYFLOAT would never overflow (since the string could not exceed 256 chars). Now it can.
-
Guy Benoish authored
-
Guy Benoish authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
-
antirez authored
Based on ideas and code in PR #5560 by @MeirShpilraien.
-
antirez authored
-
MeirShpilraien authored
-
- 13 Mar, 2019 6 commits
-
-
zhaozhao.zz authored
Fix issue #5785, in case create group on a key is not stream.
-
antirez authored
-
chendianqiang authored
-
Steve Webster authored
-
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
-
antirez authored
-