-
-
Notifications
You must be signed in to change notification settings - Fork 928
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct order of Redis zadd
dict elements
#953
Conversation
The changed `zadd()` behaviour in redis-py 3 states: https://github.com/andymccurdy/redis-py#mset-msetnx-and-zadd > For ZADD, the dict is a mapping of element-names -> score. So the dictionary generated for `zadd()` should be flipped around to have the `delivery_tag` as the key and the score as value. This commit fixes that.
Codecov Report
@@ Coverage Diff @@
## master #953 +/- ##
=======================================
Coverage 88.66% 88.66%
=======================================
Files 63 63
Lines 6512 6512
Branches 777 777
=======================================
Hits 5774 5774
Misses 656 656
Partials 82 82
Continue to review full report at Codecov.
|
Thanks! Sorry I was making the change slightly blind to both how |
Any chance to have a Pypi release of this? |
* Pins Redis library to <3.0.0 due to incompatibilities that has to be addressed in Kombu (celery/kombu#953). (closes #93)
The changed `zadd()` behaviour in redis-py 3 states: https://github.com/andymccurdy/redis-py#mset-msetnx-and-zadd > For ZADD, the dict is a mapping of element-names -> score. So the dictionary generated for `zadd()` should be flipped around to have the `delivery_tag` as the key and the score as value. This commit fixes that.
The changed
zadd()
behaviour in redis-py 3 states:https://github.com/andymccurdy/redis-py#mset-msetnx-and-zadd
So the dictionary generated for
zadd()
should be flipped around to have thedelivery_tag
as the key and the score as value. This commit fixes that.