SameerMesiah97 commented on issue #59248:
URL: https://github.com/apache/airflow/issues/59248#issuecomment-3634822808

   It appears that the PR #58746 has fixed this exact bug. The fix is present 
in release candidate 1 (rc1) for redis provider package version 4.4.1. 
   
   Please look at lines 70-73 for providers-redis/4.4.1rc 
[here](https://github.com/apache/airflow/blob/providers-redis/4.4.1rc1/providers/redis/src/airflow/providers/redis/triggers/redis_await_message.py).
 You will see the the event payloads are being decoded now. In 
providers-redis/4.3.2rc (the version you appear to be using), you will see that 
the the payloads are not being decoded. Please look at 69 onwards 
[here](https://github.com/apache/airflow/blob/providers-redis/4.3.2/providers/redis/src/airflow/providers/redis/triggers/redis_await_message.py).
   
   I have checked the trigger from providers-redis/4.4.1rc locally and it 
appears that trigger is completing successfully when I submit a JSON message to 
the redis queue. It was giving me the exact error you mentioned above when I 
did the same with earlier versions of the provider. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to