-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Fix the serialization issue of AwaitMessageTrigger with Redis. #58746
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
Conversation
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
|
jason810496
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Thanks for the fix!
It would be nice to update the corresponding unit tests as well in providers/redis/tests/unit/redis/triggers/test_redis_await_message.py, thanks!
4d58e7c to
6d85bd5
Compare
Just added a simple test that copied from the existing one. And I had a little trouble setting up a local development with dev container so that no local tests could be executed... |
f356cb6 to
c626ed3
Compare
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
This PR is trying to fix the issue of serialization on redis message for AwaitMessageTrigger: Object of type 'bytes' is not JSON serializable.
FYI, error logs without this fix as following:
Basically, the TriggerEvent couldn't be persisted due to the JSON serialiaztion error, and the triggerer instance would crash after that.
Unfortunately, all tests for AwaitMessageTrigger were mocked...