AttributeError: 'list' object has no attribute 'encode' (no support for multi-bulk reply to SUBSCRIBE command)

[marc1n]

From time to time I get error:

redis_client = redis.StrictRedis.from_url('redis://localhost:6379/0')
pubsub = redis_client.pubsub()
for message in pubsub.listen():
    # ...

Traceback (most recent call last):

 [...]
  File "<MYDIR>/local/lib/python2.7/site-packages/redis/client.py", line 2215, in listen
    response = self.handle_message(self.parse_response(block=True))
  File "<MYDIR>/local/lib/python2.7/site-packages/redis/client.py", line 2232, in handle_message
    message_type = nativestr(response[0])
  File "<MYDIR>/local/lib/python2.7/site-packages/redis/_compat.py", line 19, in <lambda>
    x if isinstance(x, str) else x.encode('utf-8', 'replace')
AttributeError: 'list' object has no attribute 'encode'

Version: redis (2.10.3)

[marc1n]

I have more information: this is happening when I subscribe more than one channel:

pubsub.subscribe('channel-1', 'channel-2')

Somtime redis server returns 2 separate responses:
['subscribe', 'channel-1', 1L]
['subscribe', 'channel-2', 1L]

Sometimes redis server returns one multi-bulk response:
[['subscribe', 'channel-1', 1L], ['subscribe', 'channel-2', 1L]]

The second case is not supported by PubSub.listen and PubSub.get_message methods.

Problem is that PubSub.handle_message() expects that response is an array with 3 strings (e.g. ['subscribe', 'channel-1', 1L]) but get array of arrays (e.g. [['subscribe', 'channel-1', 1L], ['subscribe', 'channel-2', 1L]])

[andymccurdy]

Ah, interesting. This must have changed recently in the server. Should be an easy fix.

[gugu]

@andymccurdy any update on this? Problem is still exists

[hp685]

Has anyone in this thread had any luck? I'm encountering the same issue when using redis as a backend for celery. I'm using redis(2.10.5).

[parisk]

I am running into this issue as well.

Any idea on how could this be fixed? I am willing to put a PR for that.

Sentry screenshot

[gugu]

it is celery issue – pubsub does not support concurrency and celery tries to work with it from eventlet/greenlet

[parisk]

Thanks @gugu. Makes sense. Any idea for a workaround?

[gugu]

@parisk I just published a module: https://github.com/gugu/ezy-chord
Tomorrow I'll move it to https://github.com/EzyInsights/ezy-chord

[andymccurdy]

closing this as it seems to be a celery issue. please reopen if it's something in redis-py

[davit555]

guys I think it is not celery issue.
Right now I am facing the same issue on gevent based application which is not using celery

[gugu]

It is issue of incorrect redis-py usage. Other products can use this incorrectly as well

…

On Thu, Jul 25, 2019, at 3:13 PM, David wrote: guys I think it is not celery issue. Right now I am facing the same issue on gevent based application which is not using celery — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#612>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAASLIICNMHWZWQVMIO76S3QBGKF7ANCNFSM4BBNPEDQ>.