- 11 6月, 2020 2 次提交
-
-
由 antirez 提交于
-
-
- 10 6月, 2020 2 次提交
-
-
由 antirez 提交于
-
由 Paul Spooren 提交于
The `LRANK` command returns the index (position) of a given element within a list. Using the `direction` argument it is possible to specify going from head to tail (acending, 1) or from tail to head (decending, -1). Only the first found index is returend. The complexity is O(N). When using lists as a queue it can be of interest at what position a given element is, for instance to monitor a job processing through a work queue. This came up within the Python `rq` project which is based on Redis[0]. [0]: https://github.com/rq/rq/issues/1197Signed-off-by: NPaul Spooren <mail@aparcar.org>
-
- 09 6月, 2020 2 次提交
- 08 6月, 2020 9 次提交
-
-
由 Salvatore Sanfilippo 提交于
return the correct proto version
-
由 Salvatore Sanfilippo 提交于
Don't queue commands in an already aborted MULTI state
-
由 Salvatore Sanfilippo 提交于
Avoid rejecting WATCH / UNWATCH, like MULTI/EXEC/DISCARD
-
由 Salvatore Sanfilippo 提交于
AOF: append origin SET if no expire option
-
由 Salvatore Sanfilippo 提交于
fix disconnectSlaves, to try to free each slave.
-
由 Salvatore Sanfilippo 提交于
donot free protected client in freeClientsInAsyncFreeQueue()
-
由 Oran Agra 提交于
the recent change in that loop (iteration rather than waiting for it to be empty) was intended to avoid an endless loop in case some slave would refuse to be freed. but the lookup of the first client remained, which would have caused it to try the first one again and again instead of moving on.
-
由 Oran Agra 提交于
-
由 Oran Agra 提交于
Much like MULTI/EXEC/DISCARD, the WATCH and UNWATCH are not actually operating on the database or server state, but instead operate on the client state. the client may send them all in one long pipeline and check all the responses only at the end, so failing them may lead to a mismatch between the client state on the server and the one on the client end, and execute the wrong commands (ones that were meant to be discarded) the watched keys are not actually stored in the client struct, but they are in fact part of the client state. for instance, they're not cleared or moved in SWAPDB or FLUSHDB.
-
- 07 6月, 2020 1 次提交
-
-
由 xhe 提交于
HELLO should return the current proto version, while the code hardcoded 3
-
- 06 6月, 2020 3 次提交
-
-
由 antirez 提交于
-
- 03 6月, 2020 1 次提交
-
-
由 zhaozhao.zz 提交于
-
- 02 6月, 2020 1 次提交
-
-
由 zhaozhao.zz 提交于
related #7234
-
- 31 5月, 2020 3 次提交
-
-
由 Salvatore Sanfilippo 提交于
fix pingoff test race
-
由 Oran Agra 提交于
-
由 Salvatore Sanfilippo 提交于
Fix TLS certificate loading for chained certificates.
-
- 29 5月, 2020 3 次提交
-
-
由 antirez 提交于
-
由 antirez 提交于
Now it is also possible for ACL SETUSER to accept empty strings as valid operations (doing nothing), so for instance ACL SETUSER myuser "" Will have just the effect of creating a user in the default state. This should fix #7329.
-
由 Salvatore Sanfilippo 提交于
fix clusters mixing accidentally by gossip
-
- 28 5月, 2020 9 次提交
-
-
由 antirez 提交于
This will likely avoid false positives due to trailing pings.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 Salvatore Sanfilippo 提交于
tests: each test client work on a distinct port range
-
由 Salvatore Sanfilippo 提交于
32bit CI needs to build modules correctly
-
由 Salvatore Sanfilippo 提交于
Revive and adjust meaningful offset tests
-
由 Oran Agra 提交于
these tests create several edge cases that are otherwise uncovered (at least not consistently) by the test suite, so although they're no longer testing what they were meant to test, it's still a good idea to keep them in hope that they'll expose some issue in the future.
-
由 Oran Agra 提交于
-
- 27 5月, 2020 4 次提交
-
-
由 Oran Agra 提交于
-
由 antirez 提交于
-
由 Oran Agra 提交于
i.e. don't start the search from scratch hitting the used ones again. this will also reduce the likelihood of collisions (if there are any left) by increasing the time until we re-use a port we did use in the past.
-
由 Kevin Fwu 提交于
This impacts client verification for chained certificates (such as Lets Encrypt certificates). Client Verify requires the full chain in order to properly verify the certificate.
-