The zadd call was using an incorrect variable scheme. Reference
For redis-py 4.4 the existing function parameters were invalid, I suspect this was changed at some point in the past.
recommendation
Assuming my presumption is correct, it should be possible to prevent such problems caused by API changes from arising in the future by specifying the version (or version range) of the redis-py (redis) dependency.
corrupted data
I was dealing with an old legacy dataset which had null entries for types and values, with these changes such entries are ignored instead of causing an error.
zadd
The zadd call was using an incorrect variable scheme. Reference For redis-py 4.4 the existing function parameters were invalid, I suspect this was changed at some point in the past.
recommendation
Assuming my presumption is correct, it should be possible to prevent such problems caused by API changes from arising in the future by specifying the version (or version range) of the redis-py (redis) dependency.
corrupted data
I was dealing with an old legacy dataset which had null entries for types and values, with these changes such entries are ignored instead of causing an error.