- 05 3月, 2015 1 次提交
-
-
由 antirez 提交于
Itereator misuse due to analyzeLatencyForEvent() accessing the dictionary during the iteration, without the iterator being reclared as safe.
-
- 10 2月, 2015 9 次提交
-
-
由 Charles Hooper 提交于
-
由 antirez 提交于
-
由 antirez 提交于
--stat mode already used to reconnect automatically if the server is no longer available. This is useful since this is an interactive mode used for debugging, however the same applies to --latency and --latency-dist modes, so now both use the reconnecting command execution as well. The reconnection code was modified to use basic VT100 escape sequences in order to play better with different kinds of output on the screen when the reconnection happens, and to hide the reconnection attempt output when finally the reconnection happens.
-
由 antirez 提交于
So far not able to find a color palette within the 256 colors which is not confusing. However I believe it is a possible task, so will try better later.
-
由 antirez 提交于
Still not happy with the result but low grays are hard to see in certain monitors with a non perfect gamma.
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
-
由 antirez 提交于
This test on Linux was extremely slow, since in Tcl we can't enable easily tcp-nodelay, so the busy loop used to take *a lot* with bigger writes. Fixed using pipelining.
-
- 03 2月, 2015 1 次提交
-
-
由 mattcollier 提交于
Code was adding '\n' (line 521) to the end of NIL values exlusively making csv output inconsistent. Removed '\n'
-
- 22 1月, 2015 3 次提交
-
-
由 antirez 提交于
Rationale is that when re-entering, it is likely due to Lua debugging hooks. Returning an error will be ignored in most cases, going totally unnoticed. With the log at least we leave a trace. Related to issue #2302.
-
由 antirez 提交于
Instead of calling redisPanic() to abort the server. Related to issue #2302.
-
由 antirez 提交于
Related to issue #2302.
-
- 21 1月, 2015 1 次提交
-
-
由 antirez 提交于
The cleanup code expects that if 'di' is not NULL, it is a valid iterator that should be freed. The result of this bug was a crash of the AOF rewriting process if an error occurred after the DBs data are written and the iterator is no longer valid.
-
- 09 1月, 2015 2 次提交
- 08 1月, 2015 2 次提交
-
-
由 antirez 提交于
-
由 Jungtaek Lim 提交于
-
- 23 12月, 2014 1 次提交
-
-
由 antirez 提交于
1. Server unxtime may remain not updated while loading AOF, so ETA is not updated correctly. 2. Number of processed byte was not initialized. 3. Possible division by zero condition (likely cause of issue #1932).
-
- 22 12月, 2014 1 次提交
-
-
由 Alon Diamant 提交于
-
- 19 12月, 2014 1 次提交
-
-
由 antirez 提交于
Fixes issue #2225.
-
- 17 12月, 2014 1 次提交
-
-
由 Rhommel Lamas 提交于
-
- 16 12月, 2014 1 次提交
-
-
由 antirez 提交于
-
- 13 12月, 2014 5 次提交
-
-
由 antirez 提交于
Otherwise there are security risks, especially when providing Redis as a service, the user may "sniff" for admin commands renamed to an unguessable string via rename-command in redis.conf.
-
由 antirez 提交于
The old list did not made much sense... and the flag is currently not used at all, so no side effects.
-
由 Salvatore Sanfilippo 提交于
Adds a symlink for redis-sentinel when Make install
-
由 antirez 提交于
It fixes a bad bug that crashes the server in certain conditions as shown in issue #2210.
-
由 Rhommel Lamas 提交于
-
- 11 12月, 2014 4 次提交
-
-
由 antirez 提交于
Related to #2094.
-
由 Matt Stancliff 提交于
People mostly use SORT against lists, but our prior behavior was pretending lists were an unordered bag requiring a forced-sort when no sort was requested. We can just use the native list ordering to ensure consistency across replicaion and scripting calls. Closes #2079 Closes #545 (again)
-
由 Ben Dowling 提交于
status command currently reports success when redis has crashed and the pid file still exists. Changing to check the actual process is running.
-
由 zhanghailei 提交于
-
- 09 12月, 2014 7 次提交
-
-
由 Sun He 提交于
-
由 Deepak Verma 提交于
-
由 azure provisioned user 提交于
-
由 Sun He 提交于
-
由 Sun He 提交于
-
由 Sun He 提交于
-
由 Serghei Iakovlev 提交于
Improved getting pid
-