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
{{ message }}
This repository has been archived by the owner on Feb 21, 2023. It is now read-only.
You can see that multi-exec response [b'value', b'value', b'value', [b'foo', b'val1', b'bar', b'val2']] was decoded twice. In this case decoding in RedisConnection._end_transaction is not make sense because we have already decoded it in the RedisConnection._process_data.
The text was updated successfully, but these errors were encountered:
Transaction data always decoded two times if connection encoding was defined:
Test case:
Tracing for
util.decode
You can see that
multi-exec
response[b'value', b'value', b'value', [b'foo', b'val1', b'bar', b'val2']]
was decoded twice. In this case decoding inRedisConnection._end_transaction
is not make sense because we have already decoded it in theRedisConnection._process_data
.The text was updated successfully, but these errors were encountered: