You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
valkey-java regression test use unstable valkey code, but after 3eb8314, some test fail.
➜ valkey git:(unstable) rcli
127.0.0.1:6379> set a a
OK
127.0.0.1:6379> hset b b b
(integer) 1
127.0.0.1:6379> set c c
OK
127.0.0.1:6379> sadd d d
(integer) 1
127.0.0.1:6379> set e e
OK
127.0.0.1:6379> zadd f 0 f
(integer) 1
127.0.0.1:6379> set g g
OK
127.0.0.1:6379> scan 0 count 4 type string
1) "0" // this is failure point
2) 1) "a"
2) "c"
3) "e"
4) "g"
The failure point is that cursor should not be 0, but i do not known this is right, may be it should be 0?
I also test redis latest unstable code, the result is not 0.
➜ redis git:(unstable) rcli
127.0.0.1:6379> set a a
OK
127.0.0.1:6379> hset b b b
(integer) 1
127.0.0.1:6379> set c c
OK
127.0.0.1:6379> sadd d d
(integer) 1
127.0.0.1:6379> set e e
OK
127.0.0.1:6379> zadd f 0 f
(integer) 1
127.0.0.1:6379> set g g
OK
127.0.0.1:6379> scan 0 count 4 type string
1) "1"
2) 1) "g"
2) "a"
3) "c"
4) "e"
127.0.0.1:6379>
Returned cursor 0 means all elements have been returned. It is true in this case, so I think it's not a bug.
Another correct result is a non-zero cursor and the next scan returns no elements and zero cursor. Non-zero retured cursor means there are maybe more elements.
Describe the bug
valkey-java regression test use unstable valkey code, but after 3eb8314, some test fail.
The failure point is that cursor should not be 0, but i do not known this is right, may be it should be 0?
I also test redis latest unstable code, the result is not 0.
can you have a look? @zuiderkwast
The text was updated successfully, but these errors were encountered: