antirez
e938b8a1dd
redis-cli: fix #5096 double error message.
2018-07-09 13:25:48 +02:00
antirez
846203279c
redis-cli: cliConnect() flags CC_FORCE and CC_QUIET.
...
We need CC_QUIET in order to fix #5096 by silently failing if needed.
2018-07-09 13:24:30 +02:00
antirez
375589d028
redis-cli: cliConnect() flags CC_FORCE and CC_QUIET.
...
We need CC_QUIET in order to fix #5096 by silently failing if needed.
2018-07-09 13:24:30 +02:00
Amit Dey
a3a5a25fa0
fixing broken link in CONTRIBUTING
...
http://help.github.com/send-pull-requests/
is no longer supported
this change modifies the link to the working one
https://help.github.com/articles/creating-a-pull-request/
2018-07-09 13:14:57 +02:00
Amit Dey
2a28f06a75
fixing broken link in CONTRIBUTING
...
http://help.github.com/send-pull-requests/
is no longer supported
this change modifies the link to the working one
https://help.github.com/articles/creating-a-pull-request/
2018-07-09 13:14:57 +02:00
dejun.xdj
289d8d9c2c
CLIENT UNBLOCK: fix client unblock help message.
2018-07-09 13:03:57 +02:00
dejun.xdj
5335463d44
CLIENT UNBLOCK: fix client unblock help message.
2018-07-09 13:03:57 +02:00
minkikim89
62a4a8c1d5
fix whitespace in redis-cli.c
2018-07-09 12:59:13 +02:00
minkikim89
c37742de0e
fix whitespace in redis-cli.c
2018-07-09 12:59:13 +02:00
WuYunlong
0a5805d7f1
fix compile warning in addReplySubcommandSyntaxError
2018-07-09 12:57:12 +02:00
WuYunlong
ad57103fed
fix compile warning in addReplySubcommandSyntaxError
2018-07-09 12:57:12 +02:00
antirez
cb78c84235
Use nolocks_localtime() for safer logging.
2018-07-04 16:50:22 +02:00
antirez
aefa752cf9
Use nolocks_localtime() for safer logging.
2018-07-04 16:50:22 +02:00
antirez
81778d91bf
Cache timezone and daylight active flag for safer logging.
...
With such information will be able to use a private localtime()
implementation serverLog(), which does not use any locking and is both
thread and fork() safe.
2018-07-04 16:45:00 +02:00
antirez
7604f6792f
Cache timezone and daylight active flag for safer logging.
...
With such information will be able to use a private localtime()
implementation serverLog(), which does not use any locking and is both
thread and fork() safe.
2018-07-04 16:45:00 +02:00
antirez
18d8205bbd
Localtime: clarify is_leap_year() working with comments.
2018-07-04 15:50:41 +02:00
antirez
3a6894cdd2
Localtime: clarify is_leap_year() working with comments.
2018-07-04 15:50:41 +02:00
antirez
2964414450
Localtime: fix comment about leap year.
2018-07-04 15:16:54 +02:00
antirez
e522dd5788
Localtime: fix comment about leap year.
2018-07-04 15:16:54 +02:00
antirez
0ea39aa404
Localtime: fix daylight saving adjustment. Use * not +.
2018-07-04 15:16:20 +02:00
antirez
6d1b29d7c6
Localtime: fix daylight saving adjustment. Use * not +.
2018-07-04 15:16:20 +02:00
antirez
6614d30599
Localtime: fix daylight time documentation and computation.
2018-07-04 14:09:07 +02:00
antirez
fbd7290478
Localtime: fix daylight time documentation and computation.
2018-07-04 14:09:07 +02:00
dejun.xdj
46f5a2ca07
Fix indentation.
2018-07-04 20:04:06 +08:00
dejun.xdj
aa62b5ebe9
Fix indentation.
2018-07-04 20:04:06 +08:00
antirez
243c5a7a30
Localtime: add a test main() function to check the output.
2018-07-04 13:46:31 +02:00
antirez
d21c58867e
Localtime: add a test main() function to check the output.
2018-07-04 13:46:31 +02:00
antirez
c25ee35a8b
Localtime: day of month is 1 based. Convert from 0 based "days".
2018-07-04 13:35:40 +02:00
antirez
a72f9c1931
Localtime: day of month is 1 based. Convert from 0 based "days".
2018-07-04 13:35:40 +02:00
antirez
b9f3383029
Localtime: fix timezone adjustment.
2018-07-04 13:35:15 +02:00
antirez
5caae0e6e9
Localtime: fix timezone adjustment.
2018-07-04 13:35:15 +02:00
antirez
0c12cbedbb
Localtime: compute year, month and day of the month.
2018-07-04 13:25:55 +02:00
antirez
ecba1a2fd4
Localtime: compute year, month and day of the month.
2018-07-04 13:25:55 +02:00
antirez
06ca400f95
Localtime: basics initial calculations. Year missing.
2018-07-04 13:16:53 +02:00
antirez
bb802969d7
Localtime: basics initial calculations. Year missing.
2018-07-04 13:16:53 +02:00
antirez
6a52906758
Localtime function skeleton and file added.
2018-07-04 12:56:12 +02:00
antirez
e8f72804f5
Localtime function skeleton and file added.
2018-07-04 12:56:12 +02:00
Jack Drogon
93238575f7
Fix typo
2018-07-03 18:19:46 +02:00
Jack Drogon
df7bafeb44
Fix typo
2018-07-03 18:19:46 +02:00
antirez
94b3ee6142
Clarify the pending_querybuf field of clients.
2018-07-03 13:25:41 +02:00
antirez
57dc5832a7
Clarify the pending_querybuf field of clients.
2018-07-03 13:25:41 +02:00
antirez
549b8b9973
Improve style of PR #5084 .
2018-07-03 13:23:29 +02:00
antirez
dc6c3bfe71
Improve style of PR #5084 .
2018-07-03 13:23:29 +02:00
Salvatore Sanfilippo
526b30a7ce
Merge pull request #5084 from chendq8/pending-querybuf
...
limit the size of pending-querybuf in masterclient
2018-07-03 13:19:37 +02:00
Salvatore Sanfilippo
4bcdfb0c5d
Merge pull request #5084 from chendq8/pending-querybuf
...
limit the size of pending-querybuf in masterclient
2018-07-03 13:19:37 +02:00
antirez
677d10b2a8
Set repl_down_since to zero on state change.
...
PR #5081 fixes an "interesting" bug about Redis Cluster failover but in
general about the updating of repl_down_since, that is used in order to
count the time a slave was left disconnected from its master.
While the fix provided resolves the specific issue, in general the
validity of repl_down_since is limited to states that are different
than the state CONNECTED, and the disconnected time is set when the
state is DISCONNECTED. However from CONNECTED to other states, the state
machine must always go to DISCONNECTED first. So it makes sense to set
the field to zero (since it is meaningless in that context) when the
state is set to CONNECTED.
2018-07-03 12:42:14 +02:00
antirez
32fc058177
Set repl_down_since to zero on state change.
...
PR #5081 fixes an "interesting" bug about Redis Cluster failover but in
general about the updating of repl_down_since, that is used in order to
count the time a slave was left disconnected from its master.
While the fix provided resolves the specific issue, in general the
validity of repl_down_since is limited to states that are different
than the state CONNECTED, and the disconnected time is set when the
state is DISCONNECTED. However from CONNECTED to other states, the state
machine must always go to DISCONNECTED first. So it makes sense to set
the field to zero (since it is meaningless in that context) when the
state is set to CONNECTED.
2018-07-03 12:42:14 +02:00
Salvatore Sanfilippo
02e385169e
Merge pull request #5081 from trevor211/fixClusterFailover
...
cluster failover bug
2018-07-03 12:36:53 +02:00
Salvatore Sanfilippo
c8110e814c
Merge pull request #5081 from trevor211/fixClusterFailover
...
cluster failover bug
2018-07-03 12:36:53 +02:00
chendianqiang
cbb2ac0799
Merge branch 'unstable' into pending-querybuf
2018-07-03 10:07:26 +08:00