Closed mkeemon closed 1 year ago
Hi @mkeemon
That's unexpected. I would guess something on the AWS side.
What's your aws-sdk-sqs version? Did it change recently?
Would you be able to submit a PR with the failsafe change?
We saw the same issue also start last night. There is some explanation in this issue here:
All set @phstc https://github.com/ruby-shoryuken/shoryuken/pull/753. Let me know if you need anything else or if I did something improperly!
Edit: We're using 1.67.0
of the aws-sdk-sqs
gem in multiple projects, all of which began failing last night
Last night, we saw our Shoryuken processes begin to fail with the below error. It appears that the
aws-ruby-sdk
SQS client'sreceive_message
function is sometimes returning an empty array and sometimes returningnil
. It's unclear if this is a change in theaws-sdk
gem behavior or the AWS APIs. My guess would be the latter since this happened overnight in between releases to our application.We've monkey patched this in our application for the time being: