-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
NonExistentQueue could show the queue name #1352
Comments
👍 |
The error message is written by the service, and is simply returned and raised by the SDK. That said, the error object should respond to the method begin
client.get_queue_url(queue_name: 'q-name')
rescue Aws::SQS::Errors::NonExistentQueue => error
puts "Queue #{error.context.params[:queue_name]} not found"
end |
@trevorrowe I understand that, but I was wondering if the sdk could abstract that and raise up a more explicit message, so the clients don't need to rescue, in order to raise a more descriptive error message. |
Added to feature request backlog. |
When trying to lookup for a non existent queue, the SDK raises a generic message, which does not show the queue name, and depending on the setup, it isn't straighforward to find which queue is not found. For example: shoryuken tries to load all queues specified in the
shoryuken.yml
, and raising a generic error message, would require to investigate queue by queue to find which one is not found.Currently, shoryuken rescues NonExistentQueue to give a specific message, but it would be great to have it in the SDK instead.
The text was updated successfully, but these errors were encountered: