-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
fix: Unable to forward SNS message to SQS: An error occurred (AWS.SimpleQueueService.EmptyBatchRequest) when calling the SendMessageBatch #7663
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
fix: Unable to forward SNS message to SQS: An error occurred (AWS.SimpleQueueService.EmptyBatchRequest) when calling the SendMessageBatch #7663
Conversation
β¦pleQueueService.EmptyBatchRequest) when calling the SendMessageBatch
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.
Welcome to LocalStack! Thanks for raising your first Pull Request and landing in your contributions. Our team will reach out with any reviews or feedbacks that we have shortly. We recommend joining our Slack Community and share your PR on the #community channel to share your contributions with us. Please make sure you are following our contributing guidelines and our Code of Conduct.
CLA Assistant Lite bot All contributors have signed the CLA βοΈ β |
I have read the CLA Document and I hereby sign the CLA |
Hi @onhate and thanks for your contribution! I was pretty puzzled by this bug, because as we can see in the logs of the bug report, it should not actually send work to the worker thread doing the publishing to SQS: However, after looking, it seems we have a deeper bug in there: while filtering the messages for the subscriptions, we modify the context we send to the workers while it is being processed, which leads to the issue. This PR would fix the error messages but still subscribers would not get the messages because it would be filtered when it should not, so we need to fix the underlying bug first, and then no worker would receive an empty message entries anymore. Would you mind if I open this bugfix PR pretty quickly, as it's quite a serious bug? |
thanks for the quick response @bentsku |
Hey @onhate ! |
Thank you very much @bentsku for the quick actions, I went through the code changes and I am glad I could understand it all :D |
fix for #7662