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
There is a python ORM library for redis called walrus. It has a very rich set of tests. I found this helpful in identifying problems with compatability with stock redis. https://github.com/coleifer/walrus
I was able to run these tests against your redis and it found some issues
I have verified that stock redis passes all the tests.
The tweaks I had to do to the tests was to pass in the password='foobared' to 2 places: runtests.py does a call to Redis().Info() which needs the password set, and
walrus/tests/base.py which also needs the password passed into the Redis() call.
I'd cut a bug for each issue, but I think odds are that once you get the tests running locally you'll be able to find other incompatibilities and fix them.
The text was updated successfully, but these errors were encountered:
Your docs say it supports hscan, and I did a one-off test to see it worked with 1 element. Perhaps this test may reveal a corner case your code fails at.
You're right, kvrocks hscan return not found error when the hash key was not found which not consistence with Redis. we should fix it, very very thanks for your feedback.
There is a python ORM library for redis called walrus. It has a very rich set of tests. I found this helpful in identifying problems with compatability with stock redis. https://github.com/coleifer/walrus
I was able to run these tests against your redis and it found some issues
Here is the output of the test run.
https://pastebin.com/mFfEjWPT
I have verified that stock redis passes all the tests.
The tweaks I had to do to the tests was to pass in the password='foobared' to 2 places: runtests.py does a call to Redis().Info() which needs the password set, and
walrus/tests/base.py which also needs the password passed into the Redis() call.
I'd cut a bug for each issue, but I think odds are that once you get the tests running locally you'll be able to find other incompatibilities and fix them.
The text was updated successfully, but these errors were encountered: