- 07 Jan, 2020 2 commits
- 06 Jan, 2020 1 commit
-
-
WuYunlong authored
-
- 01 Jan, 2020 1 commit
-
-
antirez authored
Likely fix #6723. This is what happens AFAIK: we enter the main loop where we expire stuff until a given percentage of keys is still found to be logically expired. There are however other potential exit conditions. However the "sampled" variable is not always incremented inside the loop, because we may found no valid slot as we scan the hash table, but just NULLs ad dict entries. So when the do/while loop condition is triggered at the end, we do (expired*100/sampled), dividing by zero if we sampled 0 keys.
-
- 29 Dec, 2019 2 commits
-
-
antirez authored
Happened when we set the name to "" to cancel the name. Was introduced during the RESP3 refactoring. See #6036.
-
antirez authored
This bug is from the first version of Redis. Probably the problem here is that before we used an SDS split function that created empty strings for additional spaces, like in "SET foo bar". AFAIK later we replaced it with the curretn sdssplitarg() API that has no such a problem. As a result, we introduced a bug, where it is no longer possible to do something like: SET foo "" Using the inline protocol. Now it is fixed.
-
- 26 Dec, 2019 2 commits
-
-
Oran Agra authored
- make lua-replicate-commands mutable (it never was, but i don't see why) - make tcp-backlog immutable (fix a recent refactory mistake) - increase the max limit of a few configs to match what they were before the recent refactory
-
Guy Benoish authored
This commit solves several edge cases that are related to exhausting the streamID limits: We should correctly calculate the succeeding streamID instead of blindly incrementing 'seq' This affects both XREAD and XADD. Other (unrelated) changes: Reply with a better error message when trying to add an entry to a stream that has exhausted last_id
-
- 20 Dec, 2019 1 commit
-
-
antirez authored
-
- 18 Dec, 2019 6 commits
-
-
antirez authored
-
antirez authored
-
antirez authored
-
zhaozhao.zz authored
-
zhaozhao.zz authored
-
- 17 Dec, 2019 11 commits
-
-
antirez authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
Madelyn Olson authored
-
- 16 Dec, 2019 1 commit
-
-
antirez authored
-
- 13 Dec, 2019 1 commit
-
-
antirez authored
-
- 12 Dec, 2019 5 commits
-
-
Yossi Gottlieb authored
With the previous API, a NULL return value was ambiguous and could represent either an old value of NULL or an error condition. The new API returns a status code and allows the old value to be returned by-reference. This commit also includes test coverage based on tests/modules/datatype.c which did not exist at the time of the original commit.
-
Oran Agra authored
since the refactory of config.c, it was initialized from config_hz in initServer but apparently that's too late since the config file loading creates objects which call LRU_CLOCK
-
antirez authored
-
antirez authored
-
Oran Agra authored
This is useful to tell redis and modules to try to avoid doing things that may increment the replication offset, and should be used when draining a master and waiting for replicas to be in perfect sync before a failover.
-
- 11 Dec, 2019 2 commits
- 09 Dec, 2019 2 commits
- 05 Dec, 2019 2 commits
-
-
Eran Liberty authored
+ memcpy(&id,ri.key,sizeof(id)); The memcpy from the key to the id reliease on the fact that this key *should* be 8 bytes long as it was entered as such a few lines up the code. BUT if someone will change the code to the point this is no longer true, current code can trash the stack which makes debugging very hard while this fix will result in some garbage id, or even page fault. Both are preferable to stack mangaling.
-
antirez authored
-
- 03 Dec, 2019 1 commit
-
-
antirez authored
-