Closed celaus closed 11 months ago
we'll definitely fix the overflow but I'm a little concerned there is another bug somewhere. Are customizing the amount of retries that are allowed, e.g.? I think the default cap is 3 so I'm not sure how we'd hit overflow there.
Any other logs you have would be very helpful.
From my quick test, we had to get to 32 retry attempts before hitting this
Haha yes, I am configuring 100 retries - although for no specific reason, I don't think we have ever hit that when not running into rate limiting.
hahaha please don't do that! I think that's very unlikely to do what you want ;-)
Fix is here: https://github.com/smithy-lang/smithy-rs/pull/3229
according to your changelog this fix has been in 0.38 so I'll close it. 👍
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Describe the bug
The program lists a lot of AWS resources and fetches various details about them, creating/cloning the clients as needed per region/resource type. It looks like that in certain scenarios this leads to a multiplication overflow.
Expected Behavior
No overflow.
Current Behavior
After many requests this randomly occurs:
Reproduction Steps
Uncertain
Possible Solution
Cap the exponential backoff waiting time?
Additional Information/Context
No response
Version
Environment details (OS name and version, etc.)
stable-aarch64-apple-darwin
Logs
No response