2011-05-24 12:40:37 -04:00
|
|
|
start_server {tags {"scripting"}} {
|
|
|
|
test {EVAL - Does Lua interpreter replies to our requests?} {
|
|
|
|
r eval {return 'hello'} 0
|
|
|
|
} {hello}
|
|
|
|
|
|
|
|
test {EVAL - Lua integer -> Redis protocol type conversion} {
|
|
|
|
r eval {return 100.5} 0
|
|
|
|
} {100}
|
|
|
|
|
|
|
|
test {EVAL - Lua string -> Redis protocol type conversion} {
|
|
|
|
r eval {return 'hello world'} 0
|
|
|
|
} {hello world}
|
|
|
|
|
|
|
|
test {EVAL - Lua true boolean -> Redis protocol type conversion} {
|
|
|
|
r eval {return true} 0
|
|
|
|
} {1}
|
|
|
|
|
|
|
|
test {EVAL - Lua false boolean -> Redis protocol type conversion} {
|
|
|
|
r eval {return false} 0
|
|
|
|
} {}
|
|
|
|
|
|
|
|
test {EVAL - Lua status code reply -> Redis protocol type conversion} {
|
|
|
|
r eval {return {ok='fine'}} 0
|
|
|
|
} {fine}
|
|
|
|
|
|
|
|
test {EVAL - Lua error reply -> Redis protocol type conversion} {
|
|
|
|
catch {
|
|
|
|
r eval {return {err='this is an error'}} 0
|
|
|
|
} e
|
|
|
|
set _ $e
|
|
|
|
} {this is an error}
|
|
|
|
|
|
|
|
test {EVAL - Lua table -> Redis protocol type conversion} {
|
|
|
|
r eval {return {1,2,3,'ciao',{1,2}}} 0
|
|
|
|
} {1 2 3 ciao {1 2}}
|
|
|
|
|
2013-01-16 12:00:20 -05:00
|
|
|
test {EVAL - Are the KEYS and ARGV arrays populated correctly?} {
|
2011-05-24 12:40:37 -04:00
|
|
|
r eval {return {KEYS[1],KEYS[2],ARGV[1],ARGV[2]}} 2 a b c d
|
|
|
|
} {a b c d}
|
|
|
|
|
|
|
|
test {EVAL - is Lua able to call Redis API?} {
|
|
|
|
r set mykey myval
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {return redis.call('get',KEYS[1])} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {myval}
|
|
|
|
|
|
|
|
test {EVALSHA - Can we call a SHA1 if already defined?} {
|
2014-04-06 10:20:01 -04:00
|
|
|
r evalsha fd758d1589d044dd850a6f05d52f2eefd27f033f 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {myval}
|
|
|
|
|
2012-11-22 09:50:00 -05:00
|
|
|
test {EVALSHA - Can we call a SHA1 in uppercase?} {
|
2014-04-06 10:20:01 -04:00
|
|
|
r evalsha FD758D1589D044DD850A6F05D52F2EEFD27F033F 1 mykey
|
2012-11-22 09:50:00 -05:00
|
|
|
} {myval}
|
|
|
|
|
2011-10-25 05:19:15 -04:00
|
|
|
test {EVALSHA - Do we get an error on invalid SHA1?} {
|
|
|
|
catch {r evalsha NotValidShaSUM 0} e
|
|
|
|
set _ $e
|
|
|
|
} {NOSCRIPT*}
|
|
|
|
|
2011-05-24 12:40:37 -04:00
|
|
|
test {EVALSHA - Do we get an error on non defined SHA1?} {
|
2011-10-25 05:19:15 -04:00
|
|
|
catch {r evalsha ffd632c7d33e571e9f24556ebed26c3479a87130 0} e
|
2011-05-24 12:40:37 -04:00
|
|
|
set _ $e
|
|
|
|
} {NOSCRIPT*}
|
|
|
|
|
|
|
|
test {EVAL - Redis integer -> Lua type conversion} {
|
2016-04-25 09:49:57 -04:00
|
|
|
r set x 0
|
2011-05-24 12:40:37 -04:00
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('incr',KEYS[1])
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 x
|
2011-05-24 12:40:37 -04:00
|
|
|
} {number 1}
|
|
|
|
|
|
|
|
test {EVAL - Redis bulk -> Lua type conversion} {
|
|
|
|
r set mykey myval
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('get',KEYS[1])
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {string myval}
|
|
|
|
|
|
|
|
test {EVAL - Redis multi bulk -> Lua type conversion} {
|
|
|
|
r del mylist
|
|
|
|
r rpush mylist a
|
|
|
|
r rpush mylist b
|
|
|
|
r rpush mylist c
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('lrange',KEYS[1],0,-1)
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo[1],foo[2],foo[3],# foo}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mylist
|
2011-05-24 12:40:37 -04:00
|
|
|
} {table a b c 3}
|
|
|
|
|
|
|
|
test {EVAL - Redis status reply -> Lua type conversion} {
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('set',KEYS[1],'myval')
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo['ok']}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {table OK}
|
|
|
|
|
|
|
|
test {EVAL - Redis error reply -> Lua type conversion} {
|
|
|
|
r set mykey myval
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('incr',KEYS[1])
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo['err']}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {table {ERR value is not an integer or out of range}}
|
|
|
|
|
|
|
|
test {EVAL - Redis nil bulk reply -> Lua type conversion} {
|
|
|
|
r del mykey
|
|
|
|
r eval {
|
2016-04-25 09:49:57 -04:00
|
|
|
local foo = redis.pcall('get',KEYS[1])
|
2011-05-24 12:40:37 -04:00
|
|
|
return {type(foo),foo == false}
|
2016-04-25 09:49:57 -04:00
|
|
|
} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {boolean 1}
|
|
|
|
|
Fix semantics of Lua calls to SELECT.
Lua scripts are executed in the context of the currently selected
database (as selected by the caller of the script).
However Lua scripts are also free to use the SELECT command in order to
affect other DBs. When SELECT is called frm Lua, the old behavior, before
this commit, was to automatically set the Lua caller selected DB to the
last DB selected by Lua. See for example the following sequence of
commands:
SELECT 0
SET x 10
EVAL "redis.call('select','1')" 0
SET x 20
Before this commit after the execution of this sequence of commands,
we'll have x=10 in DB 0, and x=20 in DB 1.
Because of the problem above, there was a bug affecting replication of
Lua scripts, because of the actual implementation of replication. It was
possible to fix the implementation of Lua scripts in order to fix the
issue, but looking closely, the bug is the consequence of the behavior
of Lua ability to set the caller's DB.
Under the old semantics, a script selecting a different DB, has no simple
ways to restore the state and select back the previously selected DB.
Moreover the script auhtor must remember that the restore is needed,
otherwise the new commands executed by the caller, will be executed in
the context of a different DB.
So this commit fixes both the replication issue, and this hard-to-use
semantics, by removing the ability of Lua, after the script execution,
to force the caller to switch to the DB selected by the Lua script.
The new behavior of the previous sequence of commadns is to just set
X=20 in DB 0. However Lua scripts are still capable of writing / reading
from different DBs if needed.
WARNING: This is a semantical change that will break programs that are
conceived to select the client selected DB via Lua scripts.
This fixes issue #1811.
2014-06-12 09:51:55 -04:00
|
|
|
test {EVAL - Is the Lua client using the currently selected DB?} {
|
2011-05-24 12:40:37 -04:00
|
|
|
r set mykey "this is DB 9"
|
|
|
|
r select 10
|
|
|
|
r set mykey "this is DB 10"
|
2016-04-25 09:49:57 -04:00
|
|
|
r eval {return redis.pcall('get',KEYS[1])} 1 mykey
|
2011-05-24 12:40:37 -04:00
|
|
|
} {this is DB 10}
|
|
|
|
|
Fix semantics of Lua calls to SELECT.
Lua scripts are executed in the context of the currently selected
database (as selected by the caller of the script).
However Lua scripts are also free to use the SELECT command in order to
affect other DBs. When SELECT is called frm Lua, the old behavior, before
this commit, was to automatically set the Lua caller selected DB to the
last DB selected by Lua. See for example the following sequence of
commands:
SELECT 0
SET x 10
EVAL "redis.call('select','1')" 0
SET x 20
Before this commit after the execution of this sequence of commands,
we'll have x=10 in DB 0, and x=20 in DB 1.
Because of the problem above, there was a bug affecting replication of
Lua scripts, because of the actual implementation of replication. It was
possible to fix the implementation of Lua scripts in order to fix the
issue, but looking closely, the bug is the consequence of the behavior
of Lua ability to set the caller's DB.
Under the old semantics, a script selecting a different DB, has no simple
ways to restore the state and select back the previously selected DB.
Moreover the script auhtor must remember that the restore is needed,
otherwise the new commands executed by the caller, will be executed in
the context of a different DB.
So this commit fixes both the replication issue, and this hard-to-use
semantics, by removing the ability of Lua, after the script execution,
to force the caller to switch to the DB selected by the Lua script.
The new behavior of the previous sequence of commadns is to just set
X=20 in DB 0. However Lua scripts are still capable of writing / reading
from different DBs if needed.
WARNING: This is a semantical change that will break programs that are
conceived to select the client selected DB via Lua scripts.
This fixes issue #1811.
2014-06-12 09:51:55 -04:00
|
|
|
test {EVAL - SELECT inside Lua should not affect the caller} {
|
|
|
|
# here we DB 10 is selected
|
|
|
|
r set mykey "original value"
|
2011-10-20 10:02:23 -04:00
|
|
|
r eval {return redis.pcall('select','9')} 0
|
Fix semantics of Lua calls to SELECT.
Lua scripts are executed in the context of the currently selected
database (as selected by the caller of the script).
However Lua scripts are also free to use the SELECT command in order to
affect other DBs. When SELECT is called frm Lua, the old behavior, before
this commit, was to automatically set the Lua caller selected DB to the
last DB selected by Lua. See for example the following sequence of
commands:
SELECT 0
SET x 10
EVAL "redis.call('select','1')" 0
SET x 20
Before this commit after the execution of this sequence of commands,
we'll have x=10 in DB 0, and x=20 in DB 1.
Because of the problem above, there was a bug affecting replication of
Lua scripts, because of the actual implementation of replication. It was
possible to fix the implementation of Lua scripts in order to fix the
issue, but looking closely, the bug is the consequence of the behavior
of Lua ability to set the caller's DB.
Under the old semantics, a script selecting a different DB, has no simple
ways to restore the state and select back the previously selected DB.
Moreover the script auhtor must remember that the restore is needed,
otherwise the new commands executed by the caller, will be executed in
the context of a different DB.
So this commit fixes both the replication issue, and this hard-to-use
semantics, by removing the ability of Lua, after the script execution,
to force the caller to switch to the DB selected by the Lua script.
The new behavior of the previous sequence of commadns is to just set
X=20 in DB 0. However Lua scripts are still capable of writing / reading
from different DBs if needed.
WARNING: This is a semantical change that will break programs that are
conceived to select the client selected DB via Lua scripts.
This fixes issue #1811.
2014-06-12 09:51:55 -04:00
|
|
|
set res [r get mykey]
|
|
|
|
r select 9
|
|
|
|
set res
|
|
|
|
} {original value}
|
2011-05-24 12:40:37 -04:00
|
|
|
|
2011-10-31 11:09:07 -04:00
|
|
|
if 0 {
|
|
|
|
test {EVAL - Script can't run more than configured time limit} {
|
|
|
|
r config set lua-time-limit 1
|
|
|
|
catch {
|
|
|
|
r eval {
|
|
|
|
local i = 0
|
|
|
|
while true do i=i+1 end
|
|
|
|
} 0
|
|
|
|
} e
|
|
|
|
set _ $e
|
|
|
|
} {*execution time*}
|
|
|
|
}
|
2011-09-27 09:39:41 -04:00
|
|
|
|
Unified MULTI, LUA, and RM_Call with respect to blocking commands (#8025)
Blocking command should not be used with MULTI, LUA, and RM_Call. This is because,
the caller, who executes the command in this context, expects a reply.
Today, LUA and MULTI have a special (and different) treatment to blocking commands:
LUA - Most commands are marked with no-script flag which are checked when executing
and command from LUA, commands that are not marked (like XREAD) verify that their
blocking mode is not used inside LUA (by checking the CLIENT_LUA client flag).
MULTI - Command that is going to block, first verify that the client is not inside
multi (by checking the CLIENT_MULTI client flag). If the client is inside multi, they
return a result which is a match to the empty key with no timeout (for example blpop
inside MULTI will act as lpop)
For modules that perform RM_Call with blocking command, the returned results type is
REDISMODULE_REPLY_UNKNOWN and the caller can not really know what happened.
Disadvantages of the current state are:
No unified approach, LUA, MULTI, and RM_Call, each has a different treatment
Module can not safely execute blocking command (and get reply or error).
Though It is true that modules are not like LUA or MULTI and should be smarter not
to execute blocking commands on RM_Call, sometimes you want to execute a command base
on client input (for example if you create a module that provides a new scripting
language like javascript or python).
While modules (on modules command) can check for REDISMODULE_CTX_FLAGS_LUA or
REDISMODULE_CTX_FLAGS_MULTI to know not to block the client, there is no way to
check if the command came from another module using RM_Call. So there is no way
for a module to know not to block another module RM_Call execution.
This commit adds a way to unify the treatment for blocking clients by introducing
a new CLIENT_DENY_BLOCKING client flag. On LUA, MULTI, and RM_Call the new flag
turned on to signify that the client should not be blocked. A blocking command
verifies that the flag is turned off before blocking. If a blocking command sees
that the CLIENT_DENY_BLOCKING flag is on, it's not blocking and return results
which are matches to empty key with no timeout (as MULTI does today).
The new flag is checked on the following commands:
List blocking commands: BLPOP, BRPOP, BRPOPLPUSH, BLMOVE,
Zset blocking commands: BZPOPMIN, BZPOPMAX
Stream blocking commands: XREAD, XREADGROUP
SUBSCRIBE, PSUBSCRIBE, MONITOR
In addition, the new flag is turned on inside the AOF client, we do not want to
block the AOF client to prevent deadlocks and commands ordering issues (and there
is also an existing assert in the code that verifies it).
To keep backward compatibility on LUA, all the no-script flags on existing commands
were kept untouched. In addition, a LUA special treatment on XREAD and XREADGROUP was kept.
To keep backward compatibility on MULTI (which today allows SUBSCRIBE, and PSUBSCRIBE).
We added a special treatment on those commands to allow executing them on MULTI.
The only backward compatibility issue that this PR introduces is that now MONITOR
is not allowed inside MULTI.
Tests were added to verify blocking commands are not blocking the client on LUA, MULTI,
or RM_Call. Tests were added to verify the module can check for CLIENT_DENY_BLOCKING flag.
Co-authored-by: Oran Agra <oran@redislabs.com>
Co-authored-by: Itamar Haber <itamar@redislabs.com>
2020-11-17 11:58:55 -05:00
|
|
|
test {EVAL - Scripts can't run blpop command} {
|
2011-09-27 09:39:41 -04:00
|
|
|
set e {}
|
2016-05-31 10:43:21 -04:00
|
|
|
catch {r eval {return redis.pcall('blpop','x',0)} 0} e
|
2011-09-27 09:39:41 -04:00
|
|
|
set e
|
|
|
|
} {*not allowed*}
|
|
|
|
|
Unified MULTI, LUA, and RM_Call with respect to blocking commands (#8025)
Blocking command should not be used with MULTI, LUA, and RM_Call. This is because,
the caller, who executes the command in this context, expects a reply.
Today, LUA and MULTI have a special (and different) treatment to blocking commands:
LUA - Most commands are marked with no-script flag which are checked when executing
and command from LUA, commands that are not marked (like XREAD) verify that their
blocking mode is not used inside LUA (by checking the CLIENT_LUA client flag).
MULTI - Command that is going to block, first verify that the client is not inside
multi (by checking the CLIENT_MULTI client flag). If the client is inside multi, they
return a result which is a match to the empty key with no timeout (for example blpop
inside MULTI will act as lpop)
For modules that perform RM_Call with blocking command, the returned results type is
REDISMODULE_REPLY_UNKNOWN and the caller can not really know what happened.
Disadvantages of the current state are:
No unified approach, LUA, MULTI, and RM_Call, each has a different treatment
Module can not safely execute blocking command (and get reply or error).
Though It is true that modules are not like LUA or MULTI and should be smarter not
to execute blocking commands on RM_Call, sometimes you want to execute a command base
on client input (for example if you create a module that provides a new scripting
language like javascript or python).
While modules (on modules command) can check for REDISMODULE_CTX_FLAGS_LUA or
REDISMODULE_CTX_FLAGS_MULTI to know not to block the client, there is no way to
check if the command came from another module using RM_Call. So there is no way
for a module to know not to block another module RM_Call execution.
This commit adds a way to unify the treatment for blocking clients by introducing
a new CLIENT_DENY_BLOCKING client flag. On LUA, MULTI, and RM_Call the new flag
turned on to signify that the client should not be blocked. A blocking command
verifies that the flag is turned off before blocking. If a blocking command sees
that the CLIENT_DENY_BLOCKING flag is on, it's not blocking and return results
which are matches to empty key with no timeout (as MULTI does today).
The new flag is checked on the following commands:
List blocking commands: BLPOP, BRPOP, BRPOPLPUSH, BLMOVE,
Zset blocking commands: BZPOPMIN, BZPOPMAX
Stream blocking commands: XREAD, XREADGROUP
SUBSCRIBE, PSUBSCRIBE, MONITOR
In addition, the new flag is turned on inside the AOF client, we do not want to
block the AOF client to prevent deadlocks and commands ordering issues (and there
is also an existing assert in the code that verifies it).
To keep backward compatibility on LUA, all the no-script flags on existing commands
were kept untouched. In addition, a LUA special treatment on XREAD and XREADGROUP was kept.
To keep backward compatibility on MULTI (which today allows SUBSCRIBE, and PSUBSCRIBE).
We added a special treatment on those commands to allow executing them on MULTI.
The only backward compatibility issue that this PR introduces is that now MONITOR
is not allowed inside MULTI.
Tests were added to verify blocking commands are not blocking the client on LUA, MULTI,
or RM_Call. Tests were added to verify the module can check for CLIENT_DENY_BLOCKING flag.
Co-authored-by: Oran Agra <oran@redislabs.com>
Co-authored-by: Itamar Haber <itamar@redislabs.com>
2020-11-17 11:58:55 -05:00
|
|
|
test {EVAL - Scripts can't run brpop command} {
|
|
|
|
set e {}
|
|
|
|
catch {r eval {return redis.pcall('brpop','empty_list',0)} 0} e
|
|
|
|
set e
|
|
|
|
} {*not allowed*}
|
|
|
|
|
|
|
|
test {EVAL - Scripts can't run brpoplpush command} {
|
|
|
|
set e {}
|
|
|
|
catch {r eval {return redis.pcall('brpoplpush','empty_list1', 'empty_list2',0)} 0} e
|
|
|
|
set e
|
|
|
|
} {*not allowed*}
|
|
|
|
|
|
|
|
test {EVAL - Scripts can't run blmove command} {
|
|
|
|
set e {}
|
|
|
|
catch {r eval {return redis.pcall('blmove','empty_list1', 'empty_list2', 'LEFT', 'LEFT', 0)} 0} e
|
|
|
|
set e
|
|
|
|
} {*not allowed*}
|
|
|
|
|
|
|
|
test {EVAL - Scripts can't run bzpopmin command} {
|
|
|
|
set e {}
|
|
|
|
catch {r eval {return redis.pcall('bzpopmin','empty_zset', 0)} 0} e
|
|
|
|
set e
|
|
|
|
} {*not allowed*}
|
|
|
|
|
|
|
|
test {EVAL - Scripts can't run bzpopmax command} {
|
|
|
|
set e {}
|
|
|
|
catch {r eval {return redis.pcall('bzpopmax','empty_zset', 0)} 0} e
|
|
|
|
set e
|
|
|
|
} {*not allowed*}
|
|
|
|
|
2020-03-26 05:49:21 -04:00
|
|
|
test {EVAL - Scripts can't run XREAD and XREADGROUP with BLOCK option} {
|
|
|
|
r del s
|
|
|
|
r xgroup create s g $ MKSTREAM
|
|
|
|
set res [r eval {return redis.pcall('xread','STREAMS','s','$')} 1 s]
|
|
|
|
assert {$res eq {}}
|
|
|
|
assert_error "*xread command is not allowed with BLOCK option from scripts" {r eval {return redis.pcall('xread','BLOCK',0,'STREAMS','s','$')} 1 s}
|
|
|
|
set res [r eval {return redis.pcall('xreadgroup','group','g','c','STREAMS','s','>')} 1 s]
|
|
|
|
assert {$res eq {}}
|
|
|
|
assert_error "*xreadgroup command is not allowed with BLOCK option from scripts" {r eval {return redis.pcall('xreadgroup','group','g','c','BLOCK',0,'STREAMS','s','>')} 1 s}
|
|
|
|
}
|
|
|
|
|
2011-09-27 09:39:41 -04:00
|
|
|
test {EVAL - Scripts can't run certain commands} {
|
|
|
|
set e {}
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 0
|
2011-09-27 09:39:41 -04:00
|
|
|
catch {
|
2011-10-20 10:02:23 -04:00
|
|
|
r eval "redis.pcall('randomkey'); return redis.pcall('set','x','ciao')" 0
|
2011-09-27 09:39:41 -04:00
|
|
|
} e
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 1
|
2011-09-27 09:39:41 -04:00
|
|
|
set e
|
|
|
|
} {*not allowed after*}
|
|
|
|
|
2012-08-31 04:22:21 -04:00
|
|
|
test {EVAL - No arguments to redis.call/pcall is considered an error} {
|
|
|
|
set e {}
|
|
|
|
catch {r eval {return redis.call()} 0} e
|
|
|
|
set e
|
|
|
|
} {*one argument*}
|
|
|
|
|
2011-10-20 10:02:23 -04:00
|
|
|
test {EVAL - redis.call variant raises a Lua error on Redis cmd error (1)} {
|
|
|
|
set e {}
|
|
|
|
catch {
|
|
|
|
r eval "redis.call('nosuchcommand')" 0
|
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*Unknown Redis*}
|
|
|
|
|
|
|
|
test {EVAL - redis.call variant raises a Lua error on Redis cmd error (1)} {
|
|
|
|
set e {}
|
|
|
|
catch {
|
|
|
|
r eval "redis.call('get','a','b','c')" 0
|
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*number of args*}
|
|
|
|
|
|
|
|
test {EVAL - redis.call variant raises a Lua error on Redis cmd error (1)} {
|
|
|
|
set e {}
|
|
|
|
r set foo bar
|
|
|
|
catch {
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {redis.call('lpush',KEYS[1],'val')} 1 foo
|
2011-10-20 10:02:23 -04:00
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*against a key*}
|
2011-10-25 05:19:15 -04:00
|
|
|
|
2014-04-04 14:13:14 -04:00
|
|
|
test {EVAL - JSON numeric decoding} {
|
|
|
|
# We must return the table as a string because otherwise
|
|
|
|
# Redis converts floats to ints and we get 0 and 1023 instead
|
|
|
|
# of 0.0003 and 1023.2 as the parsed output.
|
|
|
|
r eval {return
|
|
|
|
table.concat(
|
|
|
|
cjson.decode(
|
|
|
|
"[0.0, -5e3, -1, 0.3e-3, 1023.2, 0e10]"), " ")
|
|
|
|
} 0
|
|
|
|
} {0 -5000 -1 0.0003 1023.2 0}
|
|
|
|
|
|
|
|
test {EVAL - JSON string decoding} {
|
|
|
|
r eval {local decoded = cjson.decode('{"keya": "a", "keyb": "b"}')
|
|
|
|
return {decoded.keya, decoded.keyb}
|
|
|
|
} 0
|
|
|
|
} {a b}
|
|
|
|
|
2014-04-04 17:20:04 -04:00
|
|
|
test {EVAL - cmsgpack can pack double?} {
|
|
|
|
r eval {local encoded = cmsgpack.pack(0.1)
|
|
|
|
local h = ""
|
|
|
|
for i = 1, #encoded do
|
|
|
|
h = h .. string.format("%02x",string.byte(encoded,i))
|
|
|
|
end
|
|
|
|
return h
|
|
|
|
} 0
|
|
|
|
} {cb3fb999999999999a}
|
|
|
|
|
|
|
|
test {EVAL - cmsgpack can pack negative int64?} {
|
|
|
|
r eval {local encoded = cmsgpack.pack(-1099511627776)
|
|
|
|
local h = ""
|
|
|
|
for i = 1, #encoded do
|
|
|
|
h = h .. string.format("%02x",string.byte(encoded,i))
|
|
|
|
end
|
|
|
|
return h
|
|
|
|
} 0
|
|
|
|
} {d3ffffff0000000000}
|
|
|
|
|
|
|
|
test {EVAL - cmsgpack can pack and unpack circular references?} {
|
|
|
|
r eval {local a = {x=nil,y=5}
|
|
|
|
local b = {x=a}
|
|
|
|
a['x'] = b
|
|
|
|
local encoded = cmsgpack.pack(a)
|
|
|
|
local h = ""
|
|
|
|
-- cmsgpack encodes to a depth of 16, but can't encode
|
|
|
|
-- references, so the encoded object has a deep copy recusive
|
|
|
|
-- depth of 16.
|
|
|
|
for i = 1, #encoded do
|
|
|
|
h = h .. string.format("%02x",string.byte(encoded,i))
|
|
|
|
end
|
|
|
|
-- when unpacked, re.x.x != re because the unpack creates
|
|
|
|
-- individual tables down to a depth of 16.
|
|
|
|
-- (that's why the encoded output is so large)
|
|
|
|
local re = cmsgpack.unpack(encoded)
|
|
|
|
assert(re)
|
|
|
|
assert(re.x)
|
|
|
|
assert(re.x.x.y == re.y)
|
|
|
|
assert(re.x.x.x.x.y == re.y)
|
|
|
|
assert(re.x.x.x.x.x.x.y == re.y)
|
|
|
|
assert(re.x.x.x.x.x.x.x.x.x.x.y == re.y)
|
|
|
|
-- maximum working depth:
|
|
|
|
assert(re.x.x.x.x.x.x.x.x.x.x.x.x.x.x.y == re.y)
|
|
|
|
-- now the last x would be b above and has no y
|
|
|
|
assert(re.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x)
|
|
|
|
-- so, the final x.x is at the depth limit and was assigned nil
|
|
|
|
assert(re.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x.x == nil)
|
|
|
|
return {h, re.x.x.x.x.x.x.x.x.y == re.y, re.y == 5}
|
|
|
|
} 0
|
|
|
|
} {82a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a17882a17905a17881a178c0 1 1}
|
|
|
|
|
Lua: Add bitop
A few people have written custom C commands because bit
manipulation isn't exposed through Lua. Let's give
them Mike Pall's bitop.
This adds bitop 1.0.2 (2012-05-08) from http://bitop.luajit.org/
bitop is imported as "bit" into the global namespace.
New Lua commands: bit.tobit, bit.tohex, bit.bnot, bit.band, bit.bor, bit.bxor,
bit.lshift, bit.rshift, bit.arshift, bit.rol, bit.ror, bit.bswap
Verification of working (the asserts would abort on error, so (nil) is correct):
127.0.0.1:6379> eval "assert(bit.tobit(1) == 1); assert(bit.band(1) == 1); assert(bit.bxor(1,2) == 3); assert(bit.bor(1,2,4,8,16,32,64,128) == 255)" 0
(nil)
127.0.0.1:6379> eval 'assert(0x7fffffff == 2147483647, "broken hex literals"); assert(0xffffffff == -1 or 0xffffffff == 2^32-1, "broken hex literals"); assert(tostring(-1) == "-1", "broken tostring()"); assert(tostring(0xffffffff) == "-1" or tostring(0xffffffff) == "4294967295", "broken tostring()")' 0
(nil)
Tests also integrated into the scripting tests and can be run with:
./runtest --single unit/scripting
Tests are excerpted from `bittest.lua` included in the bitop distribution.
2014-04-04 11:34:36 -04:00
|
|
|
test {EVAL - Numerical sanity check from bitop} {
|
|
|
|
r eval {assert(0x7fffffff == 2147483647, "broken hex literals");
|
|
|
|
assert(0xffffffff == -1 or 0xffffffff == 2^32-1,
|
|
|
|
"broken hex literals");
|
|
|
|
assert(tostring(-1) == "-1", "broken tostring()");
|
|
|
|
assert(tostring(0xffffffff) == "-1" or
|
|
|
|
tostring(0xffffffff) == "4294967295",
|
|
|
|
"broken tostring()")
|
|
|
|
} 0
|
|
|
|
} {}
|
|
|
|
|
|
|
|
test {EVAL - Verify minimal bitop functionality} {
|
|
|
|
r eval {assert(bit.tobit(1) == 1);
|
|
|
|
assert(bit.band(1) == 1);
|
|
|
|
assert(bit.bxor(1,2) == 3);
|
|
|
|
assert(bit.bor(1,2,4,8,16,32,64,128) == 255)
|
|
|
|
} 0
|
|
|
|
} {}
|
|
|
|
|
2016-01-08 09:42:43 -05:00
|
|
|
test {EVAL - Able to parse trailing comments} {
|
|
|
|
r eval {return 'hello' --trailing comment} 0
|
|
|
|
} {hello}
|
|
|
|
|
2011-10-25 05:19:15 -04:00
|
|
|
test {SCRIPTING FLUSH - is able to clear the scripts cache?} {
|
|
|
|
r set mykey myval
|
2014-04-06 10:20:01 -04:00
|
|
|
set v [r evalsha fd758d1589d044dd850a6f05d52f2eefd27f033f 1 mykey]
|
2011-10-25 05:19:15 -04:00
|
|
|
assert_equal $v myval
|
|
|
|
set e ""
|
|
|
|
r script flush
|
2014-04-06 10:20:01 -04:00
|
|
|
catch {r evalsha fd758d1589d044dd850a6f05d52f2eefd27f033f 1 mykey} e
|
2011-10-25 05:19:15 -04:00
|
|
|
set e
|
|
|
|
} {NOSCRIPT*}
|
|
|
|
|
2021-01-15 08:32:58 -05:00
|
|
|
test {SCRIPTING FLUSH ASYNC} {
|
|
|
|
for {set j 0} {$j < 100} {incr j} {
|
|
|
|
r script load "return $j"
|
|
|
|
}
|
|
|
|
assert { [string match "*number_of_cached_scripts:100*" [r info Memory]] }
|
|
|
|
r script flush async
|
|
|
|
assert { [string match "*number_of_cached_scripts:0*" [r info Memory]] }
|
|
|
|
}
|
|
|
|
|
2011-10-25 05:19:15 -04:00
|
|
|
test {SCRIPT EXISTS - can detect already defined scripts?} {
|
|
|
|
r eval "return 1+1" 0
|
|
|
|
r script exists a27e7e8a43702b7046d4f6a7ccf5b60cef6b9bd9 a27e7e8a43702b7046d4f6a7ccf5b60cef6b9bda
|
|
|
|
} {1 0}
|
|
|
|
|
|
|
|
test {SCRIPT LOAD - is able to register scripts in the scripting cache} {
|
|
|
|
list \
|
|
|
|
[r script load "return 'loaded'"] \
|
|
|
|
[r evalsha b534286061d4b9e4026607613b95c06c06015ae8 0]
|
2011-10-25 08:46:15 -04:00
|
|
|
} {b534286061d4b9e4026607613b95c06c06015ae8 loaded}
|
2012-02-01 11:49:03 -05:00
|
|
|
|
|
|
|
test "In the context of Lua the output of random commands gets ordered" {
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 0
|
2012-02-01 11:49:03 -05:00
|
|
|
r del myset
|
|
|
|
r sadd myset a b c d e f g h i l m n o p q r s t u v z aa aaa azz
|
2018-09-05 13:47:29 -04:00
|
|
|
set res [r eval {return redis.call('smembers',KEYS[1])} 1 myset]
|
|
|
|
r debug lua-always-replicate-commands 1
|
|
|
|
set res
|
2012-02-01 11:49:03 -05:00
|
|
|
} {a aa aaa azz b c d e f g h i l m n o p q r s t u v z}
|
|
|
|
|
Scripting: Force SORT BY constant determinism inside SORT itself.
SORT is able to return (faster than when ordering) unordered output if
the "BY" clause is used with a constant value. However we try to play
well with scripting requirements of determinism providing always sorted
outputs when SORT (and other similar commands) are called by Lua
scripts.
However we used the general mechanism in place in scripting in order to
reorder SORT output, that is, if the command has the "S" flag set, the
Lua scripting engine will take an additional step when converting a
multi bulk reply to Lua value, calling a Lua sorting function.
This is suboptimal as we can do it faster inside SORT itself.
This is also broken as issue #545 shows us: basically when SORT is used
with a constant BY, and additionally also GET is used, the Lua scripting
engine was trying to order the output as a flat array, while it was
actually a list of key-value pairs.
What we do know is to recognized if the caller of SORT is the Lua client
(since we can check this using the REDIS_LUA_CLIENT flag). If so, and if
a "don't sort" condition is triggered by the BY option with a constant
string, we force the lexicographical sorting.
This commit fixes this bug and improves the performance, and at the same
time simplifies the implementation. This does not mean I'm smart today,
it means I was stupid when I committed the original implementation ;)
2012-09-04 19:12:41 -04:00
|
|
|
test "SORT is normally not alpha re-ordered for the scripting engine" {
|
2012-02-01 11:49:03 -05:00
|
|
|
r del myset
|
|
|
|
r sadd myset 1 2 3 4 10
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {return redis.call('sort',KEYS[1],'desc')} 1 myset
|
2012-02-01 11:49:03 -05:00
|
|
|
} {10 4 3 2 1}
|
|
|
|
|
Scripting: Force SORT BY constant determinism inside SORT itself.
SORT is able to return (faster than when ordering) unordered output if
the "BY" clause is used with a constant value. However we try to play
well with scripting requirements of determinism providing always sorted
outputs when SORT (and other similar commands) are called by Lua
scripts.
However we used the general mechanism in place in scripting in order to
reorder SORT output, that is, if the command has the "S" flag set, the
Lua scripting engine will take an additional step when converting a
multi bulk reply to Lua value, calling a Lua sorting function.
This is suboptimal as we can do it faster inside SORT itself.
This is also broken as issue #545 shows us: basically when SORT is used
with a constant BY, and additionally also GET is used, the Lua scripting
engine was trying to order the output as a flat array, while it was
actually a list of key-value pairs.
What we do know is to recognized if the caller of SORT is the Lua client
(since we can check this using the REDIS_LUA_CLIENT flag). If so, and if
a "don't sort" condition is triggered by the BY option with a constant
string, we force the lexicographical sorting.
This commit fixes this bug and improves the performance, and at the same
time simplifies the implementation. This does not mean I'm smart today,
it means I was stupid when I committed the original implementation ;)
2012-09-04 19:12:41 -04:00
|
|
|
test "SORT BY <constant> output gets ordered for scripting" {
|
2012-02-01 11:49:03 -05:00
|
|
|
r del myset
|
|
|
|
r sadd myset a b c d e f g h i l m n o p q r s t u v z aa aaa azz
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {return redis.call('sort',KEYS[1],'by','_')} 1 myset
|
2012-02-01 11:49:03 -05:00
|
|
|
} {a aa aaa azz b c d e f g h i l m n o p q r s t u v z}
|
|
|
|
|
Scripting: Force SORT BY constant determinism inside SORT itself.
SORT is able to return (faster than when ordering) unordered output if
the "BY" clause is used with a constant value. However we try to play
well with scripting requirements of determinism providing always sorted
outputs when SORT (and other similar commands) are called by Lua
scripts.
However we used the general mechanism in place in scripting in order to
reorder SORT output, that is, if the command has the "S" flag set, the
Lua scripting engine will take an additional step when converting a
multi bulk reply to Lua value, calling a Lua sorting function.
This is suboptimal as we can do it faster inside SORT itself.
This is also broken as issue #545 shows us: basically when SORT is used
with a constant BY, and additionally also GET is used, the Lua scripting
engine was trying to order the output as a flat array, while it was
actually a list of key-value pairs.
What we do know is to recognized if the caller of SORT is the Lua client
(since we can check this using the REDIS_LUA_CLIENT flag). If so, and if
a "don't sort" condition is triggered by the BY option with a constant
string, we force the lexicographical sorting.
This commit fixes this bug and improves the performance, and at the same
time simplifies the implementation. This does not mean I'm smart today,
it means I was stupid when I committed the original implementation ;)
2012-09-04 19:12:41 -04:00
|
|
|
test "SORT BY <constant> with GET gets ordered for scripting" {
|
2012-02-01 11:49:03 -05:00
|
|
|
r del myset
|
|
|
|
r sadd myset a b c
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {return redis.call('sort',KEYS[1],'by','_','get','#','get','_:*')} 1 myset
|
Scripting: Force SORT BY constant determinism inside SORT itself.
SORT is able to return (faster than when ordering) unordered output if
the "BY" clause is used with a constant value. However we try to play
well with scripting requirements of determinism providing always sorted
outputs when SORT (and other similar commands) are called by Lua
scripts.
However we used the general mechanism in place in scripting in order to
reorder SORT output, that is, if the command has the "S" flag set, the
Lua scripting engine will take an additional step when converting a
multi bulk reply to Lua value, calling a Lua sorting function.
This is suboptimal as we can do it faster inside SORT itself.
This is also broken as issue #545 shows us: basically when SORT is used
with a constant BY, and additionally also GET is used, the Lua scripting
engine was trying to order the output as a flat array, while it was
actually a list of key-value pairs.
What we do know is to recognized if the caller of SORT is the Lua client
(since we can check this using the REDIS_LUA_CLIENT flag). If so, and if
a "don't sort" condition is triggered by the BY option with a constant
string, we force the lexicographical sorting.
This commit fixes this bug and improves the performance, and at the same
time simplifies the implementation. This does not mean I'm smart today,
it means I was stupid when I committed the original implementation ;)
2012-09-04 19:12:41 -04:00
|
|
|
} {a {} b {} c {}}
|
2012-03-28 14:47:50 -04:00
|
|
|
|
|
|
|
test "redis.sha1hex() implementation" {
|
|
|
|
list [r eval {return redis.sha1hex('')} 0] \
|
|
|
|
[r eval {return redis.sha1hex('Pizza & Mandolino')} 0]
|
|
|
|
} {da39a3ee5e6b4b0d3255bfef95601890afd80709 74822d82031af7493c20eefa13bd07ec4fada82f}
|
2012-04-13 05:48:45 -04:00
|
|
|
|
|
|
|
test {Globals protection reading an undeclared global variable} {
|
|
|
|
catch {r eval {return a} 0} e
|
|
|
|
set e
|
2016-05-06 03:12:56 -04:00
|
|
|
} {*ERR*attempted to access * global*}
|
2012-04-13 05:48:45 -04:00
|
|
|
|
2012-04-13 07:40:57 -04:00
|
|
|
test {Globals protection setting an undeclared global*} {
|
2012-04-13 05:48:45 -04:00
|
|
|
catch {r eval {a=10} 0} e
|
|
|
|
set e
|
2012-04-13 07:40:57 -04:00
|
|
|
} {*ERR*attempted to create global*}
|
2012-04-13 09:23:32 -04:00
|
|
|
|
|
|
|
test {Test an example script DECR_IF_GT} {
|
|
|
|
set decr_if_gt {
|
|
|
|
local current
|
|
|
|
|
|
|
|
current = redis.call('get',KEYS[1])
|
|
|
|
if not current then return nil end
|
|
|
|
if current > ARGV[1] then
|
|
|
|
return redis.call('decr',KEYS[1])
|
|
|
|
else
|
|
|
|
return redis.call('get',KEYS[1])
|
|
|
|
end
|
|
|
|
}
|
|
|
|
r set foo 5
|
|
|
|
set res {}
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
lappend res [r eval $decr_if_gt 1 foo 2]
|
|
|
|
set res
|
|
|
|
} {4 3 2 2 2}
|
2012-04-18 17:50:16 -04:00
|
|
|
|
|
|
|
test {Scripting engine resets PRNG at every script execution} {
|
|
|
|
set rand1 [r eval {return tostring(math.random())} 0]
|
|
|
|
set rand2 [r eval {return tostring(math.random())} 0]
|
|
|
|
assert_equal $rand1 $rand2
|
|
|
|
}
|
|
|
|
|
|
|
|
test {Scripting engine PRNG can be seeded correctly} {
|
|
|
|
set rand1 [r eval {
|
|
|
|
math.randomseed(ARGV[1]); return tostring(math.random())
|
|
|
|
} 0 10]
|
|
|
|
set rand2 [r eval {
|
|
|
|
math.randomseed(ARGV[1]); return tostring(math.random())
|
|
|
|
} 0 10]
|
|
|
|
set rand3 [r eval {
|
|
|
|
math.randomseed(ARGV[1]); return tostring(math.random())
|
|
|
|
} 0 20]
|
|
|
|
assert_equal $rand1 $rand2
|
|
|
|
assert {$rand2 ne $rand3}
|
|
|
|
}
|
2013-06-19 12:53:07 -04:00
|
|
|
|
2013-08-30 02:59:11 -04:00
|
|
|
test {EVAL does not leak in the Lua stack} {
|
|
|
|
r set x 0
|
|
|
|
# Use a non blocking client to speedup the loop.
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
for {set j 0} {$j < 10000} {incr j} {
|
|
|
|
$rd eval {return redis.call("incr",KEYS[1])} 1 x
|
|
|
|
}
|
|
|
|
for {set j 0} {$j < 10000} {incr j} {
|
|
|
|
$rd read
|
|
|
|
}
|
|
|
|
assert {[s used_memory_lua] < 1024*100}
|
|
|
|
$rd close
|
|
|
|
r get x
|
|
|
|
} {10000}
|
|
|
|
|
2013-06-19 12:53:07 -04:00
|
|
|
test {EVAL processes writes from AOF in read-only slaves} {
|
|
|
|
r flushall
|
|
|
|
r config set appendonly yes
|
2018-03-25 07:03:38 -04:00
|
|
|
r config set aof-use-rdb-preamble no
|
2014-04-06 10:20:01 -04:00
|
|
|
r eval {redis.call("set",KEYS[1],"100")} 1 foo
|
|
|
|
r eval {redis.call("incr",KEYS[1])} 1 foo
|
|
|
|
r eval {redis.call("incr",KEYS[1])} 1 foo
|
2013-06-19 12:53:07 -04:00
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[s aof_rewrite_in_progress] == 0
|
|
|
|
} else {
|
|
|
|
fail "AOF rewrite can't complete after CONFIG SET appendonly yes."
|
|
|
|
}
|
|
|
|
r config set slave-read-only yes
|
|
|
|
r slaveof 127.0.0.1 0
|
|
|
|
r debug loadaof
|
2014-05-07 10:04:45 -04:00
|
|
|
set res [r get foo]
|
|
|
|
r slaveof no one
|
|
|
|
set res
|
2013-06-19 12:53:07 -04:00
|
|
|
} {102}
|
2021-02-15 10:20:03 -05:00
|
|
|
r config set aof-use-rdb-preamble yes
|
2014-05-07 10:04:45 -04:00
|
|
|
|
2020-10-01 04:27:45 -04:00
|
|
|
test {EVAL timeout from AOF} {
|
|
|
|
# generate a long running script that is propagated to the AOF as script
|
|
|
|
# make sure that the script times out during loading
|
|
|
|
r config set appendonly no
|
|
|
|
r config set aof-use-rdb-preamble no
|
|
|
|
r config set lua-replicate-commands no
|
|
|
|
r flushall
|
|
|
|
r config set appendonly yes
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[s aof_rewrite_in_progress] == 0
|
|
|
|
} else {
|
|
|
|
fail "AOF rewrite can't complete after CONFIG SET appendonly yes."
|
|
|
|
}
|
|
|
|
r config set lua-time-limit 1
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
set start [clock clicks -milliseconds]
|
|
|
|
$rd eval {redis.call('set',KEYS[1],'y'); for i=1,1500000 do redis.call('ping') end return 'ok'} 1 x
|
|
|
|
$rd flush
|
|
|
|
after 100
|
|
|
|
catch {r ping} err
|
|
|
|
assert_match {BUSY*} $err
|
|
|
|
$rd read
|
|
|
|
set elapsed [expr [clock clicks -milliseconds]-$start]
|
|
|
|
if {$::verbose} { puts "script took $elapsed milliseconds" }
|
|
|
|
set start [clock clicks -milliseconds]
|
|
|
|
$rd debug loadaof
|
|
|
|
$rd flush
|
|
|
|
after 100
|
|
|
|
catch {r ping} err
|
|
|
|
assert_match {LOADING*} $err
|
|
|
|
$rd read
|
|
|
|
set elapsed [expr [clock clicks -milliseconds]-$start]
|
|
|
|
if {$::verbose} { puts "loading took $elapsed milliseconds" }
|
|
|
|
$rd close
|
|
|
|
r get x
|
|
|
|
} {y}
|
|
|
|
|
2014-05-07 10:04:45 -04:00
|
|
|
test {We can call scripts rewriting client->argv from Lua} {
|
|
|
|
r del myset
|
|
|
|
r sadd myset a b c
|
|
|
|
r mset a 1 b 2 c 3 d 4
|
|
|
|
assert {[r spop myset] ne {}}
|
2014-03-11 10:38:55 -04:00
|
|
|
assert {[r spop myset 1] ne {}}
|
2014-05-07 10:04:45 -04:00
|
|
|
assert {[r spop myset] ne {}}
|
|
|
|
assert {[r mget a b c d] eq {1 2 3 4}}
|
|
|
|
assert {[r spop myset] eq {}}
|
|
|
|
}
|
2014-05-20 10:20:16 -04:00
|
|
|
|
|
|
|
test {Call Redis command with many args from Lua (issue #1764)} {
|
|
|
|
r eval {
|
|
|
|
local i
|
|
|
|
local x={}
|
|
|
|
redis.call('del','mylist')
|
|
|
|
for i=1,100 do
|
|
|
|
table.insert(x,i)
|
|
|
|
end
|
|
|
|
redis.call('rpush','mylist',unpack(x))
|
|
|
|
return redis.call('lrange','mylist',0,-1)
|
|
|
|
} 0
|
|
|
|
} {1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100}
|
2014-06-04 12:51:20 -04:00
|
|
|
|
|
|
|
test {Number conversion precision test (issue #1118)} {
|
|
|
|
r eval {
|
|
|
|
local value = 9007199254740991
|
|
|
|
redis.call("set","foo",value)
|
|
|
|
return redis.call("get","foo")
|
|
|
|
} 0
|
|
|
|
} {9007199254740991}
|
2014-06-10 14:21:37 -04:00
|
|
|
|
|
|
|
test {String containing number precision test (regression of issue #1118)} {
|
|
|
|
r eval {
|
|
|
|
redis.call("set", "key", "12039611435714932082")
|
|
|
|
return redis.call("get", "key")
|
|
|
|
} 0
|
|
|
|
} {12039611435714932082}
|
2014-06-28 22:20:44 -04:00
|
|
|
|
|
|
|
test {Verify negative arg count is error instead of crash (issue #1842)} {
|
|
|
|
catch { r eval { return "hello" } -12 } e
|
|
|
|
set e
|
|
|
|
} {ERR Number of keys can't be negative}
|
2014-08-17 10:32:26 -04:00
|
|
|
|
|
|
|
test {Correct handling of reused argv (issue #1939)} {
|
|
|
|
r eval {
|
|
|
|
for i = 0, 10 do
|
|
|
|
redis.call('SET', 'a', '1')
|
|
|
|
redis.call('MGET', 'a', 'b', 'c')
|
|
|
|
redis.call('EXPIRE', 'a', 0)
|
|
|
|
redis.call('GET', 'a')
|
|
|
|
redis.call('MGET', 'a', 'b', 'c')
|
|
|
|
end
|
|
|
|
} 0
|
|
|
|
}
|
2015-10-30 05:02:10 -04:00
|
|
|
|
|
|
|
test {Functions in the Redis namespace are able to report errors} {
|
|
|
|
catch {
|
|
|
|
r eval {
|
|
|
|
redis.sha1hex()
|
|
|
|
} 0
|
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*wrong number*}
|
2021-01-05 01:29:20 -05:00
|
|
|
|
|
|
|
test {Script with RESP3 map} {
|
|
|
|
set expected_dict [dict create field value]
|
|
|
|
set expected_list [list field value]
|
|
|
|
|
|
|
|
# Sanity test for RESP3 without scripts
|
|
|
|
r HELLO 3
|
|
|
|
r hset hash field value
|
|
|
|
set res [r hgetall hash]
|
|
|
|
assert_equal $res $expected_dict
|
|
|
|
|
|
|
|
# Test RESP3 client with script in both RESP2 and RESP3 modes
|
|
|
|
set res [r eval {redis.setresp(3); return redis.call('hgetall', KEYS[1])} 1 hash]
|
|
|
|
assert_equal $res $expected_dict
|
|
|
|
set res [r eval {redis.setresp(2); return redis.call('hgetall', KEYS[1])} 1 hash]
|
|
|
|
assert_equal $res $expected_list
|
|
|
|
|
|
|
|
# Test RESP2 client with script in both RESP2 and RESP3 modes
|
|
|
|
r HELLO 2
|
|
|
|
set res [r eval {redis.setresp(3); return redis.call('hgetall', KEYS[1])} 1 hash]
|
|
|
|
assert_equal $res $expected_list
|
|
|
|
set res [r eval {redis.setresp(2); return redis.call('hgetall', KEYS[1])} 1 hash]
|
|
|
|
assert_equal $res $expected_list
|
|
|
|
}
|
2011-05-24 12:40:37 -04:00
|
|
|
}
|
2011-07-15 11:41:40 -04:00
|
|
|
|
2012-04-19 17:49:33 -04:00
|
|
|
# Start a new server since the last test in this stanza will kill the
|
|
|
|
# instance at all.
|
|
|
|
start_server {tags {"scripting"}} {
|
|
|
|
test {Timedout read-only scripts can be killed by SCRIPT KILL} {
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
r config set lua-time-limit 10
|
|
|
|
$rd eval {while true do end} 0
|
|
|
|
after 200
|
|
|
|
catch {r ping} e
|
|
|
|
assert_match {BUSY*} $e
|
|
|
|
r script kill
|
2014-04-24 12:21:12 -04:00
|
|
|
after 200 ; # Give some time to Lua to call the hook again...
|
2012-04-19 17:49:33 -04:00
|
|
|
assert_equal [r ping] "PONG"
|
|
|
|
}
|
|
|
|
|
2021-03-17 12:52:11 -04:00
|
|
|
test {Timedout read-only scripts can be killed by SCRIPT KILL even when use pcall} {
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
r config set lua-time-limit 10
|
|
|
|
$rd eval {local f = function() while 1 do redis.call('ping') end end while 1 do pcall(f) end} 0
|
|
|
|
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[catch {r ping} e] == 1
|
|
|
|
} else {
|
|
|
|
fail "Can't wait for script to start running"
|
|
|
|
}
|
|
|
|
catch {r ping} e
|
|
|
|
assert_match {BUSY*} $e
|
|
|
|
|
|
|
|
r script kill
|
|
|
|
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[catch {r ping} e] == 0
|
|
|
|
} else {
|
|
|
|
fail "Can't wait for script to be killed"
|
|
|
|
}
|
|
|
|
assert_equal [r ping] "PONG"
|
|
|
|
|
|
|
|
catch {$rd read} res
|
|
|
|
$rd close
|
|
|
|
|
|
|
|
assert_match {*killed by user*} $res
|
|
|
|
}
|
|
|
|
|
2013-01-10 05:10:31 -05:00
|
|
|
test {Timedout script link is still usable after Lua returns} {
|
|
|
|
r config set lua-time-limit 10
|
|
|
|
r eval {for i=1,100000 do redis.call('ping') end return 'ok'} 0
|
|
|
|
r ping
|
|
|
|
} {PONG}
|
|
|
|
|
2012-04-19 17:49:33 -04:00
|
|
|
test {Timedout scripts that modified data can't be killed by SCRIPT KILL} {
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
r config set lua-time-limit 10
|
2014-04-06 10:20:01 -04:00
|
|
|
$rd eval {redis.call('set',KEYS[1],'y'); while true do end} 1 x
|
2012-04-19 17:49:33 -04:00
|
|
|
after 200
|
|
|
|
catch {r ping} e
|
|
|
|
assert_match {BUSY*} $e
|
|
|
|
catch {r script kill} e
|
2012-10-22 04:28:54 -04:00
|
|
|
assert_match {UNKILLABLE*} $e
|
2012-04-19 17:49:33 -04:00
|
|
|
catch {r ping} e
|
|
|
|
assert_match {BUSY*} $e
|
|
|
|
}
|
|
|
|
|
2013-01-10 05:10:31 -05:00
|
|
|
# Note: keep this test at the end of this server stanza because it
|
|
|
|
# kills the server.
|
2012-04-19 17:49:33 -04:00
|
|
|
test {SHUTDOWN NOSAVE can kill a timedout script anyway} {
|
Squash merging 125 typo/grammar/comment/doc PRs (#7773)
List of squashed commits or PRs
===============================
commit 66801ea
Author: hwware <wen.hui.ware@gmail.com>
Date: Mon Jan 13 00:54:31 2020 -0500
typo fix in acl.c
commit 46f55db
Author: Itamar Haber <itamar@redislabs.com>
Date: Sun Sep 6 18:24:11 2020 +0300
Updates a couple of comments
Specifically:
* RM_AutoMemory completed instead of pointing to docs
* Updated link to custom type doc
commit 61a2aa0
Author: xindoo <xindoo@qq.com>
Date: Tue Sep 1 19:24:59 2020 +0800
Correct errors in code comments
commit a5871d1
Author: yz1509 <pro-756@qq.com>
Date: Tue Sep 1 18:36:06 2020 +0800
fix typos in module.c
commit 41eede7
Author: bookug <bookug@qq.com>
Date: Sat Aug 15 01:11:33 2020 +0800
docs: fix typos in comments
commit c303c84
Author: lazy-snail <ws.niu@outlook.com>
Date: Fri Aug 7 11:15:44 2020 +0800
fix spelling in redis.conf
commit 1eb76bf
Author: zhujian <zhujianxyz@gmail.com>
Date: Thu Aug 6 15:22:10 2020 +0800
add a missing 'n' in comment
commit 1530ec2
Author: Daniel Dai <764122422@qq.com>
Date: Mon Jul 27 00:46:35 2020 -0400
fix spelling in tracking.c
commit e517b31
Author: Hunter-Chen <huntcool001@gmail.com>
Date: Fri Jul 17 22:33:32 2020 +0800
Update redis.conf
Co-authored-by: Itamar Haber <itamar@redislabs.com>
commit c300eff
Author: Hunter-Chen <huntcool001@gmail.com>
Date: Fri Jul 17 22:33:23 2020 +0800
Update redis.conf
Co-authored-by: Itamar Haber <itamar@redislabs.com>
commit 4c058a8
Author: 陈浩鹏 <chenhaopeng@heytea.com>
Date: Thu Jun 25 19:00:56 2020 +0800
Grammar fix and clarification
commit 5fcaa81
Author: bodong.ybd <bodong.ybd@alibaba-inc.com>
Date: Fri Jun 19 10:09:00 2020 +0800
Fix typos
commit 4caca9a
Author: Pruthvi P <pruthvi@ixigo.com>
Date: Fri May 22 00:33:22 2020 +0530
Fix typo eviciton => eviction
commit b2a25f6
Author: Brad Dunbar <dunbarb2@gmail.com>
Date: Sun May 17 12:39:59 2020 -0400
Fix a typo.
commit 12842ae
Author: hwware <wen.hui.ware@gmail.com>
Date: Sun May 3 17:16:59 2020 -0400
fix spelling in redis conf
commit ddba07c
Author: Chris Lamb <chris@chris-lamb.co.uk>
Date: Sat May 2 23:25:34 2020 +0100
Correct a "conflicts" spelling error.
commit 8fc7bf2
Author: Nao YONASHIRO <yonashiro@r.recruit.co.jp>
Date: Thu Apr 30 10:25:27 2020 +0900
docs: fix EXPIRE_FAST_CYCLE_DURATION to ACTIVE_EXPIRE_CYCLE_FAST_DURATION
commit 9b2b67a
Author: Brad Dunbar <dunbarb2@gmail.com>
Date: Fri Apr 24 11:46:22 2020 -0400
Fix a typo.
commit 0746f10
Author: devilinrust <63737265+devilinrust@users.noreply.github.com>
Date: Thu Apr 16 00:17:53 2020 +0200
Fix typos in server.c
commit 92b588d
Author: benjessop12 <56115861+benjessop12@users.noreply.github.com>
Date: Mon Apr 13 13:43:55 2020 +0100
Fix spelling mistake in lazyfree.c
commit 1da37aa
Merge: 2d4ba28 af347a8
Author: hwware <wen.hui.ware@gmail.com>
Date: Thu Mar 5 22:41:31 2020 -0500
Merge remote-tracking branch 'upstream/unstable' into expiretypofix
commit 2d4ba28
Author: hwware <wen.hui.ware@gmail.com>
Date: Mon Mar 2 00:09:40 2020 -0500
fix typo in expire.c
commit 1a746f7
Author: SennoYuki <minakami1yuki@gmail.com>
Date: Thu Feb 27 16:54:32 2020 +0800
fix typo
commit 8599b1a
Author: dongheejeong <donghee950403@gmail.com>
Date: Sun Feb 16 20:31:43 2020 +0000
Fix typo in server.c
commit f38d4e8
Author: hwware <wen.hui.ware@gmail.com>
Date: Sun Feb 2 22:58:38 2020 -0500
fix typo in evict.c
commit fe143fc
Author: Leo Murillo <leonardo.murillo@gmail.com>
Date: Sun Feb 2 01:57:22 2020 -0600
Fix a few typos in redis.conf
commit 1ab4d21
Author: viraja1 <anchan.viraj@gmail.com>
Date: Fri Dec 27 17:15:58 2019 +0530
Fix typo in Latency API docstring
commit ca1f70e
Author: gosth <danxuedexing@qq.com>
Date: Wed Dec 18 15:18:02 2019 +0800
fix typo in sort.c
commit a57c06b
Author: ZYunH <zyunhjob@163.com>
Date: Mon Dec 16 22:28:46 2019 +0800
fix-zset-typo
commit b8c92b5
Author: git-hulk <hulk.website@gmail.com>
Date: Mon Dec 16 15:51:42 2019 +0800
FIX: typo in cluster.c, onformation->information
commit 9dd981c
Author: wujm2007 <jim.wujm@gmail.com>
Date: Mon Dec 16 09:37:52 2019 +0800
Fix typo
commit e132d7a
Author: Sebastien Williams-Wynn <s.williamswynn.mail@gmail.com>
Date: Fri Nov 15 00:14:07 2019 +0000
Minor typo change
commit 47f44d5
Author: happynote3966 <01ssrmikururudevice01@gmail.com>
Date: Mon Nov 11 22:08:48 2019 +0900
fix comment typo in redis-cli.c
commit b8bdb0d
Author: fulei <fulei@kuaishou.com>
Date: Wed Oct 16 18:00:17 2019 +0800
Fix a spelling mistake of comments in defragDictBucketCallback
commit 0def46a
Author: fulei <fulei@kuaishou.com>
Date: Wed Oct 16 13:09:27 2019 +0800
fix some spelling mistakes of comments in defrag.c
commit f3596fd
Author: Phil Rajchgot <tophil@outlook.com>
Date: Sun Oct 13 02:02:32 2019 -0400
Typo and grammar fixes
Redis and its documentation are great -- just wanted to submit a few corrections in the spirit of Hacktoberfest. Thanks for all your work on this project. I use it all the time and it works beautifully.
commit 2b928cd
Author: KangZhiDong <worldkzd@gmail.com>
Date: Sun Sep 1 07:03:11 2019 +0800
fix typos
commit 33aea14
Author: Axlgrep <axlgrep@gmail.com>
Date: Tue Aug 27 11:02:18 2019 +0800
Fixed eviction spelling issues
commit e282a80
Author: Simen Flatby <simen@oms.no>
Date: Tue Aug 20 15:25:51 2019 +0200
Update comments to reflect prop name
In the comments the prop is referenced as replica-validity-factor,
but it is really named cluster-replica-validity-factor.
commit 74d1f9a
Author: Jim Green <jimgreen2013@qq.com>
Date: Tue Aug 20 20:00:31 2019 +0800
fix comment error, the code is ok
commit eea1407
Author: Liao Tonglang <liaotonglang@gmail.com>
Date: Fri May 31 10:16:18 2019 +0800
typo fix
fix cna't to can't
commit 0da553c
Author: KAWACHI Takashi <tkawachi@gmail.com>
Date: Wed Jul 17 00:38:16 2019 +0900
Fix typo
commit 7fc8fb6
Author: Michael Prokop <mika@grml.org>
Date: Tue May 28 17:58:42 2019 +0200
Typo fixes
s/familar/familiar/
s/compatiblity/compatibility/
s/ ot / to /
s/itsef/itself/
commit 5f46c9d
Author: zhumoing <34539422+zhumoing@users.noreply.github.com>
Date: Tue May 21 21:16:50 2019 +0800
typo-fixes
typo-fixes
commit 321dfe1
Author: wxisme <850885154@qq.com>
Date: Sat Mar 16 15:10:55 2019 +0800
typo fix
commit b4fb131
Merge: 267e0e6 3df1eb8
Author: Nikitas Bastas <nikitasbst@gmail.com>
Date: Fri Feb 8 22:55:45 2019 +0200
Merge branch 'unstable' of antirez/redis into unstable
commit 267e0e6
Author: Nikitas Bastas <nikitasbst@gmail.com>
Date: Wed Jan 30 21:26:04 2019 +0200
Minor typo fix
commit 30544e7
Author: inshal96 <39904558+inshal96@users.noreply.github.com>
Date: Fri Jan 4 16:54:50 2019 +0500
remove an extra 'a' in the comments
commit 337969d
Author: BrotherGao <yangdongheng11@gmail.com>
Date: Sat Dec 29 12:37:29 2018 +0800
fix typo in redis.conf
commit 9f4b121
Merge: 423a030 e504583
Author: BrotherGao <yangdongheng@xiaomi.com>
Date: Sat Dec 29 11:41:12 2018 +0800
Merge branch 'unstable' of antirez/redis into unstable
commit 423a030
Merge: 42b02b7 46a51cd
Author: 杨东衡 <yangdongheng@xiaomi.com>
Date: Tue Dec 4 23:56:11 2018 +0800
Merge branch 'unstable' of antirez/redis into unstable
commit 42b02b7
Merge: 68c0e6e b8febe6
Author: Dongheng Yang <yangdongheng11@gmail.com>
Date: Sun Oct 28 15:54:23 2018 +0800
Merge pull request #1 from antirez/unstable
update local data
commit 714b589
Author: Christian <crifei93@gmail.com>
Date: Fri Dec 28 01:17:26 2018 +0100
fix typo "resulution"
commit e23259d
Author: garenchan <1412950785@qq.com>
Date: Wed Dec 26 09:58:35 2018 +0800
fix typo: segfauls -> segfault
commit a9359f8
Author: xjp <jianping_xie@aliyun.com>
Date: Tue Dec 18 17:31:44 2018 +0800
Fixed REDISMODULE_H spell bug
commit a12c3e4
Author: jdiaz <jrd.palacios@gmail.com>
Date: Sat Dec 15 23:39:52 2018 -0600
Fixes hyperloglog hash function comment block description
commit 770eb11
Author: 林上耀 <1210tom@163.com>
Date: Sun Nov 25 17:16:10 2018 +0800
fix typo
commit fd97fbb
Author: Chris Lamb <chris@chris-lamb.co.uk>
Date: Fri Nov 23 17:14:01 2018 +0100
Correct "unsupported" typo.
commit a85522d
Author: Jungnam Lee <jungnam.lee@oracle.com>
Date: Thu Nov 8 23:01:29 2018 +0900
fix typo in test comments
commit ade8007
Author: Arun Kumar <palerdot@users.noreply.github.com>
Date: Tue Oct 23 16:56:35 2018 +0530
Fixed grammatical typo
Fixed typo for word 'dictionary'
commit 869ee39
Author: Hamid Alaei <hamid.a85@gmail.com>
Date: Sun Aug 12 16:40:02 2018 +0430
fix documentations: (ThreadSafeContextStart/Stop -> ThreadSafeContextLock/Unlock), minor typo
commit f89d158
Author: Mayank Jain <mayankjain255@gmail.com>
Date: Tue Jul 31 23:01:21 2018 +0530
Updated README.md with some spelling corrections.
Made correction in spelling of some misspelled words.
commit 892198e
Author: dsomeshwar <someshwar.dhayalan@gmail.com>
Date: Sat Jul 21 23:23:04 2018 +0530
typo fix
commit 8a4d780
Author: Itamar Haber <itamar@redislabs.com>
Date: Mon Apr 30 02:06:52 2018 +0300
Fixes some typos
commit e3acef6
Author: Noah Rosamilia <ivoahivoah@gmail.com>
Date: Sat Mar 3 23:41:21 2018 -0500
Fix typo in /deps/README.md
commit 04442fb
Author: WuYunlong <xzsyeb@126.com>
Date: Sat Mar 3 10:32:42 2018 +0800
Fix typo in readSyncBulkPayload() comment.
commit 9f36880
Author: WuYunlong <xzsyeb@126.com>
Date: Sat Mar 3 10:20:37 2018 +0800
replication.c comment: run_id -> replid.
commit f866b4a
Author: Francesco 'makevoid' Canessa <makevoid@gmail.com>
Date: Thu Feb 22 22:01:56 2018 +0000
fix comment typo in server.c
commit 0ebc69b
Author: 줍 <jubee0124@gmail.com>
Date: Mon Feb 12 16:38:48 2018 +0900
Fix typo in redis.conf
Fix `five behaviors` to `eight behaviors` in [this sentence ](antirez/redis@unstable/redis.conf#L564)
commit b50a620
Author: martinbroadhurst <martinbroadhurst@users.noreply.github.com>
Date: Thu Dec 28 12:07:30 2017 +0000
Fix typo in valgrind.sup
commit 7d8f349
Author: Peter Boughton <peter@sorcerersisle.com>
Date: Mon Nov 27 19:52:19 2017 +0000
Update CONTRIBUTING; refer doc updates to redis-doc repo.
commit 02dec7e
Author: Klauswk <klauswk1@hotmail.com>
Date: Tue Oct 24 16:18:38 2017 -0200
Fix typo in comment
commit e1efbc8
Author: chenshi <baiwfg2@gmail.com>
Date: Tue Oct 3 18:26:30 2017 +0800
Correct two spelling errors of comments
commit 93327d8
Author: spacewander <spacewanderlzx@gmail.com>
Date: Wed Sep 13 16:47:24 2017 +0800
Update the comment for OBJ_ENCODING_EMBSTR_SIZE_LIMIT's value
The value of OBJ_ENCODING_EMBSTR_SIZE_LIMIT is 44 now instead of 39.
commit 63d361f
Author: spacewander <spacewanderlzx@gmail.com>
Date: Tue Sep 12 15:06:42 2017 +0800
Fix <prevlen> related doc in ziplist.c
According to the definition of ZIP_BIG_PREVLEN and other related code,
the guard of single byte <prevlen> should be 254 instead of 255.
commit ebe228d
Author: hanael80 <hanael80@gmail.com>
Date: Tue Aug 15 09:09:40 2017 +0900
Fix typo
commit 6b696e6
Author: Matt Robenolt <matt@ydekproductions.com>
Date: Mon Aug 14 14:50:47 2017 -0700
Fix typo in LATENCY DOCTOR output
commit a2ec6ae
Author: caosiyang <caosiyang@qiyi.com>
Date: Tue Aug 15 14:15:16 2017 +0800
Fix a typo: form => from
commit 3ab7699
Author: caosiyang <caosiyang@qiyi.com>
Date: Thu Aug 10 18:40:33 2017 +0800
Fix a typo: replicationFeedSlavesFromMaster() => replicationFeedSlavesFromMasterStream()
commit 72d43ef
Author: caosiyang <caosiyang@qiyi.com>
Date: Tue Aug 8 15:57:25 2017 +0800
fix a typo: servewr => server
commit 707c958
Author: Bo Cai <charpty@gmail.com>
Date: Wed Jul 26 21:49:42 2017 +0800
redis-cli.c typo: conut -> count.
Signed-off-by: Bo Cai <charpty@gmail.com>
commit b9385b2
Author: JackDrogon <jack.xsuperman@gmail.com>
Date: Fri Jun 30 14:22:31 2017 +0800
Fix some spell problems
commit 20d9230
Author: akosel <aaronjkosel@gmail.com>
Date: Sun Jun 4 19:35:13 2017 -0500
Fix typo
commit b167bfc
Author: Krzysiek Witkowicz <krzysiekwitkowicz@gmail.com>
Date: Mon May 22 21:32:27 2017 +0100
Fix #4008 small typo in comment
commit 2b78ac8
Author: Jake Clarkson <jacobwclarkson@gmail.com>
Date: Wed Apr 26 15:49:50 2017 +0100
Correct typo in tests/unit/hyperloglog.tcl
commit b0f1cdb
Author: Qi Luo <qiluo-msft@users.noreply.github.com>
Date: Wed Apr 19 14:25:18 2017 -0700
Fix typo
commit a90b0f9
Author: charsyam <charsyam@naver.com>
Date: Thu Mar 16 18:19:53 2017 +0900
fix typos
fix typos
fix typos
commit 8430a79
Author: Richard Hart <richardhart92@gmail.com>
Date: Mon Mar 13 22:17:41 2017 -0400
Fixed log message typo in listenToPort.
commit 481a1c2
Author: Vinod Kumar <kumar003vinod@gmail.com>
Date: Sun Jan 15 23:04:51 2017 +0530
src/db.c: Correct "save" -> "safe" typo
commit 586b4d3
Author: wangshaonan <wshn13@gmail.com>
Date: Wed Dec 21 20:28:27 2016 +0800
Fix typo they->the in helloworld.c
commit c1c4b5e
Author: Jenner <hypxm@qq.com>
Date: Mon Dec 19 16:39:46 2016 +0800
typo error
commit 1ee1a3f
Author: tielei <43289893@qq.com>
Date: Mon Jul 18 13:52:25 2016 +0800
fix some comments
commit 11a41fb
Author: Otto Kekäläinen <otto@seravo.fi>
Date: Sun Jul 3 10:23:55 2016 +0100
Fix spelling in documentation and comments
commit 5fb5d82
Author: francischan <f1ancis621@gmail.com>
Date: Tue Jun 28 00:19:33 2016 +0800
Fix outdated comments about redis.c file.
It should now refer to server.c file.
commit 6b254bc
Author: lmatt-bit <lmatt123n@gmail.com>
Date: Thu Apr 21 21:45:58 2016 +0800
Refine the comment of dictRehashMilliseconds func
SLAVECONF->REPLCONF in comment - by andyli029
commit ee9869f
Author: clark.kang <charsyam@naver.com>
Date: Tue Mar 22 11:09:51 2016 +0900
fix typos
commit f7b3b11
Author: Harisankar H <harisankarh@gmail.com>
Date: Wed Mar 9 11:49:42 2016 +0530
Typo correction: "faield" --> "failed"
Typo correction: "faield" --> "failed"
commit 3fd40fc
Author: Itamar Haber <itamar@redislabs.com>
Date: Thu Feb 25 10:31:51 2016 +0200
Fixes a typo in comments
commit 621c160
Author: Prayag Verma <prayag.verma@gmail.com>
Date: Mon Feb 1 12:36:20 2016 +0530
Fix typo in Readme.md
Spelling mistakes -
`eviciton` > `eviction`
`familar` > `familiar`
commit d7d07d6
Author: WonCheol Lee <toctoc21c@gmail.com>
Date: Wed Dec 30 15:11:34 2015 +0900
Typo fixed
commit a4dade7
Author: Felix Bünemann <buenemann@louis.info>
Date: Mon Dec 28 11:02:55 2015 +0100
[ci skip] Improve supervised upstart config docs
This mentions that "expect stop" is required for supervised upstart
to work correctly. See http://upstart.ubuntu.com/cookbook/#expect-stop
for an explanation.
commit d9caba9
Author: daurnimator <quae@daurnimator.com>
Date: Mon Dec 21 18:30:03 2015 +1100
README: Remove trailing whitespace
commit 72d42e5
Author: daurnimator <quae@daurnimator.com>
Date: Mon Dec 21 18:29:32 2015 +1100
README: Fix typo. th => the
commit dd6e957
Author: daurnimator <quae@daurnimator.com>
Date: Mon Dec 21 18:29:20 2015 +1100
README: Fix typo. familar => familiar
commit 3a12b23
Author: daurnimator <quae@daurnimator.com>
Date: Mon Dec 21 18:28:54 2015 +1100
README: Fix typo. eviciton => eviction
commit 2d1d03b
Author: daurnimator <quae@daurnimator.com>
Date: Mon Dec 21 18:21:45 2015 +1100
README: Fix typo. sever => server
commit 3973b06
Author: Itamar Haber <itamar@garantiadata.com>
Date: Sat Dec 19 17:01:20 2015 +0200
Typo fix
commit 4f2e460
Author: Steve Gao <fu@2token.com>
Date: Fri Dec 4 10:22:05 2015 +0800
Update README - fix typos
commit b21667c
Author: binyan <binbin.yan@nokia.com>
Date: Wed Dec 2 22:48:37 2015 +0800
delete redundancy color judge in sdscatcolor
commit 88894c7
Author: binyan <binbin.yan@nokia.com>
Date: Wed Dec 2 22:14:42 2015 +0800
the example output shoule be HelloWorld
commit 2763470
Author: binyan <binbin.yan@nokia.com>
Date: Wed Dec 2 17:41:39 2015 +0800
modify error word keyevente
Signed-off-by: binyan <binbin.yan@nokia.com>
commit 0847b3d
Author: Bruno Martins <bscmartins@gmail.com>
Date: Wed Nov 4 11:37:01 2015 +0000
typo
commit bbb9e9e
Author: dawedawe <dawedawe@gmx.de>
Date: Fri Mar 27 00:46:41 2015 +0100
typo: zimap -> zipmap
commit 5ed297e
Author: Axel Advento <badwolf.bloodseeker.rev@gmail.com>
Date: Tue Mar 3 15:58:29 2015 +0800
Fix 'salve' typos to 'slave'
commit edec9d6
Author: LudwikJaniuk <ludvig.janiuk@gmail.com>
Date: Wed Jun 12 14:12:47 2019 +0200
Update README.md
Co-Authored-By: Qix <Qix-@users.noreply.github.com>
commit 692a7af
Author: LudwikJaniuk <ludvig.janiuk@gmail.com>
Date: Tue May 28 14:32:04 2019 +0200
grammar
commit d962b0a
Author: Nick Frost <nickfrostatx@gmail.com>
Date: Wed Jul 20 15:17:12 2016 -0700
Minor grammar fix
commit 24fff01aaccaf5956973ada8c50ceb1462e211c6 (typos)
Author: Chad Miller <chadm@squareup.com>
Date: Tue Sep 8 13:46:11 2020 -0400
Fix faulty comment about operation of unlink()
commit 3cd5c1f3326c52aa552ada7ec797c6bb16452355
Author: Kevin <kevin.xgr@gmail.com>
Date: Wed Nov 20 00:13:50 2019 +0800
Fix typo in server.c.
From a83af59 Mon Sep 17 00:00:00 2001
From: wuwo <wuwo@wacai.com>
Date: Fri, 17 Mar 2017 20:37:45 +0800
Subject: [PATCH] falure to failure
From c961896 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E5=B7=A6=E6=87=B6?= <veficos@gmail.com>
Date: Sat, 27 May 2017 15:33:04 +0800
Subject: [PATCH] fix typo
From e600ef2 Mon Sep 17 00:00:00 2001
From: "rui.zou" <rui.zou@yunify.com>
Date: Sat, 30 Sep 2017 12:38:15 +0800
Subject: [PATCH] fix a typo
From c7d07fa Mon Sep 17 00:00:00 2001
From: Alexandre Perrin <alex@kaworu.ch>
Date: Thu, 16 Aug 2018 10:35:31 +0200
Subject: [PATCH] deps README.md typo
From b25cb67 Mon Sep 17 00:00:00 2001
From: Guy Korland <gkorland@gmail.com>
Date: Wed, 26 Sep 2018 10:55:37 +0300
Subject: [PATCH 1/2] fix typos in header
From ad28ca6 Mon Sep 17 00:00:00 2001
From: Guy Korland <gkorland@gmail.com>
Date: Wed, 26 Sep 2018 11:02:36 +0300
Subject: [PATCH 2/2] fix typos
commit 34924cdedd8552466fc22c1168d49236cb7ee915
Author: Adrian Lynch <adi_ady_ade@hotmail.com>
Date: Sat Apr 4 21:59:15 2015 +0100
Typos fixed
commit fd2a1e7
Author: Jan <jsteemann@users.noreply.github.com>
Date: Sat Oct 27 19:13:01 2018 +0200
Fix typos
Fix typos
commit e14e47c1a234b53b0e103c5f6a1c61481cbcbb02
Author: Andy Lester <andy@petdance.com>
Date: Fri Aug 2 22:30:07 2019 -0500
Fix multiple misspellings of "following"
commit 79b948ce2dac6b453fe80995abbcaac04c213d5a
Author: Andy Lester <andy@petdance.com>
Date: Fri Aug 2 22:24:28 2019 -0500
Fix misspelling of create-cluster
commit 1fffde52666dc99ab35efbd31071a4c008cb5a71
Author: Andy Lester <andy@petdance.com>
Date: Wed Jul 31 17:57:56 2019 -0500
Fix typos
commit 204c9ba9651e9e05fd73936b452b9a30be456cfe
Author: Xiaobo Zhu <xiaobo.zhu@shopee.com>
Date: Tue Aug 13 22:19:25 2019 +0800
fix typos
Squashed commit of the following:
commit 1d9aaf8
Author: danmedani <danmedani@gmail.com>
Date: Sun Aug 2 11:40:26 2015 -0700
README typo fix.
Squashed commit of the following:
commit 32bfa7c
Author: Erik Dubbelboer <erik@dubbelboer.com>
Date: Mon Jul 6 21:15:08 2015 +0200
Fixed grammer
Squashed commit of the following:
commit b24f69c
Author: Sisir Koppaka <sisir.koppaka@gmail.com>
Date: Mon Mar 2 22:38:45 2015 -0500
utils/hashtable/rehashing.c: Fix typos
Squashed commit of the following:
commit 4e04082
Author: Erik Dubbelboer <erik@dubbelboer.com>
Date: Mon Mar 23 08:22:21 2015 +0000
Small config file documentation improvements
Squashed commit of the following:
commit acb8773
Author: ctd1500 <ctd1500@gmail.com>
Date: Fri May 8 01:52:48 2015 -0700
Typo and grammar fixes in readme
commit 2eb75b6
Author: ctd1500 <ctd1500@gmail.com>
Date: Fri May 8 01:36:18 2015 -0700
fixed redis.conf comment
Squashed commit of the following:
commit a8249a2
Author: Masahiko Sawada <sawada.mshk@gmail.com>
Date: Fri Dec 11 11:39:52 2015 +0530
Revise correction of typos.
Squashed commit of the following:
commit 3c02028
Author: zhaojun11 <zhaojun11@jd.com>
Date: Wed Jan 17 19:05:28 2018 +0800
Fix typos include two code typos in cluster.c and latency.c
Squashed commit of the following:
commit 9dba47c
Author: q191201771 <191201771@qq.com>
Date: Sat Jan 4 11:31:04 2020 +0800
fix function listCreate comment in adlist.c
Update src/server.c
commit 2c7c2cb536e78dd211b1ac6f7bda00f0f54faaeb
Author: charpty <charpty@gmail.com>
Date: Tue May 1 23:16:59 2018 +0800
server.c typo: modules system dictionary type comment
Signed-off-by: charpty <charpty@gmail.com>
commit a8395323fb63cb59cb3591cb0f0c8edb7c29a680
Author: Itamar Haber <itamar@redislabs.com>
Date: Sun May 6 00:25:18 2018 +0300
Updates test_helper.tcl's help with undocumented options
Specifically:
* Host
* Port
* Client
commit bde6f9ced15755cd6407b4af7d601b030f36d60b
Author: wxisme <850885154@qq.com>
Date: Wed Aug 8 15:19:19 2018 +0800
fix comments in deps files
commit 3172474ba991532ab799ee1873439f3402412331
Author: wxisme <850885154@qq.com>
Date: Wed Aug 8 14:33:49 2018 +0800
fix some comments
commit 01b6f2b6858b5cf2ce4ad5092d2c746e755f53f0
Author: Thor Juhasz <thor@juhasz.pro>
Date: Sun Nov 18 14:37:41 2018 +0100
Minor fixes to comments
Found some parts a little unclear on a first read, which prompted me to have a better look at the file and fix some minor things I noticed.
Fixing minor typos and grammar. There are no changes to configuration options.
These changes are only meant to help the user better understand the explanations to the various configuration options
2020-09-10 06:43:38 -04:00
|
|
|
# The server should be still unresponding to normal commands.
|
2012-04-19 17:49:33 -04:00
|
|
|
catch {r ping} e
|
|
|
|
assert_match {BUSY*} $e
|
|
|
|
catch {r shutdown nosave}
|
|
|
|
# Make sure the server was killed
|
|
|
|
catch {set rd [redis_deferring_client]} e
|
|
|
|
assert_match {*connection refused*} $e
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-10-30 05:18:25 -04:00
|
|
|
foreach cmdrepl {0 1} {
|
|
|
|
start_server {tags {"scripting repl"}} {
|
|
|
|
start_server {} {
|
|
|
|
if {$cmdrepl == 1} {
|
2019-11-19 20:14:59 -05:00
|
|
|
set rt "(commands replication)"
|
2012-06-02 17:29:57 -04:00
|
|
|
} else {
|
2015-10-30 05:18:25 -04:00
|
|
|
set rt "(scripts replication)"
|
|
|
|
r debug lua-always-replicate-commands 1
|
2012-06-02 17:29:57 -04:00
|
|
|
}
|
2011-07-15 11:41:40 -04:00
|
|
|
|
2018-09-11 04:57:50 -04:00
|
|
|
test "Before the replica connects we issue two EVAL commands $rt" {
|
2015-10-30 05:18:25 -04:00
|
|
|
# One with an error, but still executing a command.
|
|
|
|
# SHA is: 67164fc43fa971f76fd1aaeeaf60c1c178d25876
|
|
|
|
catch {
|
|
|
|
r eval {redis.call('incr',KEYS[1]); redis.call('nonexisting')} 1 x
|
|
|
|
}
|
|
|
|
# One command is correct:
|
|
|
|
# SHA is: 6f5ade10a69975e903c6d07b10ea44c6382381a5
|
|
|
|
r eval {return redis.call('incr',KEYS[1])} 1 x
|
|
|
|
} {2}
|
|
|
|
|
2018-09-11 04:57:50 -04:00
|
|
|
test "Connect a replica to the master instance $rt" {
|
2015-10-30 05:18:25 -04:00
|
|
|
r -1 slaveof [srv 0 host] [srv 0 port]
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[s -1 role] eq {slave} &&
|
|
|
|
[string match {*master_link_status:up*} [r -1 info replication]]
|
|
|
|
} else {
|
2018-09-11 04:57:50 -04:00
|
|
|
fail "Can't turn the instance into a replica"
|
2015-10-30 05:18:25 -04:00
|
|
|
}
|
2013-01-10 05:10:31 -05:00
|
|
|
}
|
2011-07-15 11:41:40 -04:00
|
|
|
|
2015-10-30 05:18:25 -04:00
|
|
|
test "Now use EVALSHA against the master, with both SHAs $rt" {
|
|
|
|
# The server should replicate successful and unsuccessful
|
|
|
|
# commands as EVAL instead of EVALSHA.
|
|
|
|
catch {
|
|
|
|
r evalsha 67164fc43fa971f76fd1aaeeaf60c1c178d25876 1 x
|
|
|
|
}
|
|
|
|
r evalsha 6f5ade10a69975e903c6d07b10ea44c6382381a5 1 x
|
|
|
|
} {4}
|
|
|
|
|
|
|
|
test "If EVALSHA was replicated as EVAL, 'x' should be '4' $rt" {
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 get x] eq {4}
|
|
|
|
} else {
|
|
|
|
fail "Expected 4 in x, but value is '[r -1 get x]'"
|
|
|
|
}
|
2012-04-26 05:16:52 -04:00
|
|
|
}
|
A reimplementation of blocking operation internals.
Redis provides support for blocking operations such as BLPOP or BRPOP.
This operations are identical to normal LPOP and RPOP operations as long
as there are elements in the target list, but if the list is empty they
block waiting for new data to arrive to the list.
All the clients blocked waiting for th same list are served in a FIFO
way, so the first that blocked is the first to be served when there is
more data pushed by another client into the list.
The previous implementation of blocking operations was conceived to
serve clients in the context of push operations. For for instance:
1) There is a client "A" blocked on list "foo".
2) The client "B" performs `LPUSH foo somevalue`.
3) The client "A" is served in the context of the "B" LPUSH,
synchronously.
Processing things in a synchronous way was useful as if "A" pushes a
value that is served by "B", from the point of view of the database is a
NOP (no operation) thing, that is, nothing is replicated, nothing is
written in the AOF file, and so forth.
However later we implemented two things:
1) Variadic LPUSH that could add multiple values to a list in the
context of a single call.
2) BRPOPLPUSH that was a version of BRPOP that also provided a "PUSH"
side effect when receiving data.
This forced us to make the synchronous implementation more complex. If
client "B" is waiting for data, and "A" pushes three elemnents in a
single call, we needed to propagate an LPUSH with a missing argument
in the AOF and replication link. We also needed to make sure to
replicate the LPUSH side of BRPOPLPUSH, but only if in turn did not
happened to serve another blocking client into another list ;)
This were complex but with a few of mutually recursive functions
everything worked as expected... until one day we introduced scripting
in Redis.
Scripting + synchronous blocking operations = Issue #614.
Basically you can't "rewrite" a script to have just a partial effect on
the replicas and AOF file if the script happened to serve a few blocked
clients.
The solution to all this problems, implemented by this commit, is to
change the way we serve blocked clients. Instead of serving the blocked
clients synchronously, in the context of the command performing the PUSH
operation, it is now an asynchronous and iterative process:
1) If a key that has clients blocked waiting for data is the subject of
a list push operation, We simply mark keys as "ready" and put it into a
queue.
2) Every command pushing stuff on lists, as a variadic LPUSH, a script,
or whatever it is, is replicated verbatim without any rewriting.
3) Every time a Redis command, a MULTI/EXEC block, or a script,
completed its execution, we run the list of keys ready to serve blocked
clients (as more data arrived), and process this list serving the
blocked clients.
4) As a result of "3" maybe more keys are ready again for other clients
(as a result of BRPOPLPUSH we may have push operations), so we iterate
back to step "3" if it's needed.
The new code has a much simpler semantics, and a simpler to understand
implementation, with the disadvantage of not being able to "optmize out"
a PUSH+BPOP as a No OP.
This commit will be tested with care before the final merge, more tests
will be added likely.
2012-09-04 04:37:49 -04:00
|
|
|
|
2015-10-30 05:18:25 -04:00
|
|
|
test "Replication of script multiple pushes to list with BLPOP $rt" {
|
|
|
|
set rd [redis_deferring_client]
|
|
|
|
$rd brpop a 0
|
|
|
|
r eval {
|
|
|
|
redis.call("lpush",KEYS[1],"1");
|
|
|
|
redis.call("lpush",KEYS[1],"2");
|
|
|
|
} 1 a
|
|
|
|
set res [$rd read]
|
|
|
|
$rd close
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 lrange a 0 -1] eq [r lrange a 0 -1]
|
|
|
|
} else {
|
2018-09-11 04:57:50 -04:00
|
|
|
fail "Expected list 'a' in replica and master to be the same, but they are respectively '[r -1 lrange a 0 -1]' and '[r lrange a 0 -1]'"
|
2015-10-30 05:18:25 -04:00
|
|
|
}
|
|
|
|
set res
|
|
|
|
} {a 1}
|
|
|
|
|
|
|
|
test "EVALSHA replication when first call is readonly $rt" {
|
|
|
|
r del x
|
|
|
|
r eval {if tonumber(ARGV[1]) > 0 then redis.call('incr', KEYS[1]) end} 1 x 0
|
|
|
|
r evalsha 6e0e2745aa546d0b50b801a20983b70710aef3ce 1 x 0
|
|
|
|
r evalsha 6e0e2745aa546d0b50b801a20983b70710aef3ce 1 x 1
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 get x] eq {1}
|
|
|
|
} else {
|
|
|
|
fail "Expected 1 in x, but value is '[r -1 get x]'"
|
|
|
|
}
|
2014-02-13 06:25:44 -05:00
|
|
|
}
|
2014-06-12 10:20:30 -04:00
|
|
|
|
2015-10-30 05:18:25 -04:00
|
|
|
test "Lua scripts using SELECT are replicated correctly $rt" {
|
|
|
|
r eval {
|
|
|
|
redis.call("set","foo1","bar1")
|
|
|
|
redis.call("select","10")
|
|
|
|
redis.call("incr","x")
|
|
|
|
redis.call("select","11")
|
|
|
|
redis.call("incr","z")
|
|
|
|
} 0
|
|
|
|
r eval {
|
|
|
|
redis.call("set","foo1","bar1")
|
|
|
|
redis.call("select","10")
|
|
|
|
redis.call("incr","x")
|
|
|
|
redis.call("select","11")
|
|
|
|
redis.call("incr","z")
|
|
|
|
} 0
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 debug digest] eq [r debug digest]
|
|
|
|
} else {
|
2018-09-11 04:57:50 -04:00
|
|
|
fail "Master-Replica desync after Lua script using SELECT."
|
2015-10-30 05:18:25 -04:00
|
|
|
}
|
2014-06-12 10:20:30 -04:00
|
|
|
}
|
|
|
|
}
|
2011-07-15 11:41:40 -04:00
|
|
|
}
|
|
|
|
}
|
2015-10-30 07:02:15 -04:00
|
|
|
|
|
|
|
start_server {tags {"scripting repl"}} {
|
2018-03-25 07:03:38 -04:00
|
|
|
start_server {overrides {appendonly yes aof-use-rdb-preamble no}} {
|
2018-09-11 04:57:50 -04:00
|
|
|
test "Connect a replica to the master instance" {
|
2015-10-30 07:02:15 -04:00
|
|
|
r -1 slaveof [srv 0 host] [srv 0 port]
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[s -1 role] eq {slave} &&
|
|
|
|
[string match {*master_link_status:up*} [r -1 info replication]]
|
|
|
|
} else {
|
2018-09-11 04:57:50 -04:00
|
|
|
fail "Can't turn the instance into a replica"
|
2015-10-30 07:02:15 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
test "Redis.replicate_commands() must be issued before any write" {
|
|
|
|
r eval {
|
|
|
|
redis.call('set','foo','bar');
|
|
|
|
return redis.replicate_commands();
|
|
|
|
} 0
|
|
|
|
} {}
|
|
|
|
|
|
|
|
test "Redis.replicate_commands() must be issued before any write (2)" {
|
|
|
|
r eval {
|
|
|
|
return redis.replicate_commands();
|
|
|
|
} 0
|
|
|
|
} {1}
|
|
|
|
|
|
|
|
test "Redis.set_repl() must be issued after replicate_commands()" {
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 0
|
2015-10-30 07:02:15 -04:00
|
|
|
catch {
|
|
|
|
r eval {
|
|
|
|
redis.set_repl(redis.REPL_ALL);
|
|
|
|
} 0
|
|
|
|
} e
|
2018-09-05 13:47:29 -04:00
|
|
|
r debug lua-always-replicate-commands 1
|
2015-10-30 07:02:15 -04:00
|
|
|
set e
|
|
|
|
} {*only after turning on*}
|
|
|
|
|
|
|
|
test "Redis.set_repl() don't accept invalid values" {
|
|
|
|
catch {
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
redis.set_repl(12345);
|
|
|
|
} 0
|
|
|
|
} e
|
|
|
|
set e
|
|
|
|
} {*Invalid*flags*}
|
|
|
|
|
|
|
|
test "Test selective replication of certain Redis commands from Lua" {
|
|
|
|
r del a b c d
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
redis.call('set','a','1');
|
|
|
|
redis.set_repl(redis.REPL_NONE);
|
|
|
|
redis.call('set','b','2');
|
|
|
|
redis.set_repl(redis.REPL_AOF);
|
|
|
|
redis.call('set','c','3');
|
|
|
|
redis.set_repl(redis.REPL_ALL);
|
|
|
|
redis.call('set','d','4');
|
|
|
|
} 0
|
|
|
|
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r -1 mget a b c d] eq {1 {} {} 4}
|
|
|
|
} else {
|
2018-09-11 04:57:50 -04:00
|
|
|
fail "Only a and c should be replicated to replica"
|
2015-10-30 07:02:15 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
# Master should have everything right now
|
|
|
|
assert {[r mget a b c d] eq {1 2 3 4}}
|
|
|
|
|
|
|
|
# After an AOF reload only a, c and d should exist
|
|
|
|
r debug loadaof
|
|
|
|
|
|
|
|
assert {[r mget a b c d] eq {1 {} 3 4}}
|
|
|
|
}
|
|
|
|
|
|
|
|
test "PRNG is seeded randomly for command replication" {
|
|
|
|
set a [
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
return math.random()*100000;
|
|
|
|
} 0
|
|
|
|
]
|
|
|
|
set b [
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
return math.random()*100000;
|
|
|
|
} 0
|
|
|
|
]
|
|
|
|
assert {$a ne $b}
|
|
|
|
}
|
|
|
|
|
|
|
|
test "Using side effects is not a problem with command replication" {
|
|
|
|
r eval {
|
|
|
|
redis.replicate_commands();
|
|
|
|
redis.call('set','time',redis.call('time')[1])
|
|
|
|
} 0
|
|
|
|
|
|
|
|
assert {[r get time] ne {}}
|
|
|
|
|
|
|
|
wait_for_condition 50 100 {
|
|
|
|
[r get time] eq [r -1 get time]
|
|
|
|
} else {
|
2018-09-11 04:57:50 -04:00
|
|
|
fail "Time key does not match between master and replica"
|
2015-10-30 07:02:15 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2020-02-04 03:34:11 -05:00
|
|
|
start_server {tags {"scripting"}} {
|
|
|
|
r script debug sync
|
|
|
|
r eval {return 'hello'} 0
|
|
|
|
r eval {return 'hello'} 0
|
|
|
|
}
|