Skip to content

Conversation

prcyangli
Copy link
Contributor

when the key is expire or deleted, the valure is not null string
so when s.IsNotFound(), set the value to null string

skip key even though the pattern does not match
fix setbit coredump,when setbit key 1  1
when the key is expire or deleted, the valure is not null string
so when s.IsNotFound(), set the value to null string
@prcyangli prcyangli changed the title fux bitset and bitget bug when the key is expire or deleted … when the key is expire or deleted, the valure is not null string so when s.IsNotFound(), set the value to null string fux bitset and bitget bug when the key is expire or deleted Feb 5, 2018
@leviathan0992
Copy link
Contributor

  • 当key被删除之后,value返回的是"",你可以自己测一下
  • nemo的master分支count的用法是正确的

@prcyangli
Copy link
Contributor Author

sscan 和setbit coredump的问题之前提交过,github不太熟悉,不清楚这次为什么有显示
setbit key被删除后是没问题的,
setbit key如果是被过期是有问题的
127.0.0.1:9221> SETBIT mybit 10 1
(integer) 0
127.0.0.1:9221> getbit mybit 10
(integer) 1
127.0.0.1:9221> EXPIRE mybit 10
(integer) 1
127.0.0.1:9221> ttl mybit
(integer) -2
127.0.0.1:9221> getbit mybit 10
(integer) 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants