wait_until(:table_not_exists… shows an error for a non existing table
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start at the Aws::DynamoDB::Client#wait_until entry point and reproduce the table_not_exists case from the issue. Trace how ResourceNotFoundException is handled for a missing table, then verify that the waiter returns nil without showing a client error.
Written by the indexing model from the issue text.
Description
Describe the bug
When I call Aws::DynamoDB::Client.new.wait_until(:table_not_exists, table_name: 'this_does_not_exist')
then I see a client error
[Aws::DynamoDB::Client 400 0.004513 0 retries] describe_table(table_name:"this_does_not_exist") Aws::DynamoDB::Errors::ResourceNotFoundException Cannot do operations on a non-existent table
IMHO this is unexpected behavior. When I tell the client to wait until a table does not exist (e.g. after a delete call) and it doesnt exist, it should just silently proceed.
Regression Issue
- Select this option if this issue appears to be a regression.
Expected Behavior
Just return nil, do not show a DynamoDB Client error
Current Behavior
Shows client error.
Reproduction Steps
Aws::DynamoDB::Client.new.wait_until(:table_not_exists, table_name: 'this_does_not_exist')
Possible Solution
No response
Additional Information/Context
No response
Gem name ('aws-sdk', 'aws-sdk-resources' or service gems like 'aws-sdk-s3') and its version
aws-sdk-ruby
Environment details (Version of Ruby, OS environment)
latest, latest macOS
- Dominant language
- Ruby
- Stars
- 3.7k
- Forks
- 1.2k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 25
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aws/aws-sdk-ruby
-
service-api
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aws/aws-sdk-ruby#3395 · 1 comment ·
Maintainers usually reply within 1 day
-
BedrockAgentCore: invoke_agent_runtime buffers entire response instead of streaming in real-timeOpendocumentation p3 queued
Difficulty 4/5 3-5 days Newbie friendliness 48/100
aws/aws-sdk-ruby#3348 · 6 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
feature-request needs-major-version
Difficulty 3/5 1-2 days Newbie friendliness 48/100
aws/aws-sdk-ruby#3241 · 5 comments ·
Maintainers usually reply within 1 day
-
investigating service-api
Difficulty 4/5 3-5 days Newbie friendliness 35/100
aws/aws-sdk-ruby#3217 · 4 comments ·
Maintainers usually reply within 1 day
-
service-api
Difficulty 5/5 Over a week Newbie friendliness 25/100
aws/aws-sdk-ruby#3191 · 1 comment ·
Maintainers usually reply within 1 day
All issues in aws/aws-sdk-ruby
Similar issues
-
Lint/NoReturnInMemoization flags `return` in local variable `||=` and `&&=` assignmentsPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Shopify/ruby-style-guide#815 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
zerocracy/judges-action#2849 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bigbluebutton/bigbluebutton#26166 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
TarteelAI/quranic-universal-library#916 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day