waitUntilObjectExists throws WaiterConfiguration.minDelay must be greater than 0 when minDelay is 0.5

[razbensimon]

Checkboxes for prior research

• I've gone through Developer Guide and API reference
• I've checked AWS Forums and StackOverflow.
• I've searched for previous similar issues and didn't find any solution.

Describe the bug

waitUntilObjectExists method throws WaiterConfiguration.minDelay must be greater than 0 error if minDelay is 0.5.
I see you are using @smithy/util-waiter which throws it here.

0.5 is greater than 0, the condition and error are not synced.

This means that I can't wait for an s3 object with an exponential backoff policy to start at 0.5 seconds.

Is there any workaround?

Regression Issue

• Select this option if this issue appears to be a regression.

SDK version number

@aws-sdk/[email protected]

Which JavaScript Runtime is this issue in?

Node.js

Details of the browser/Node.js/ReactNative version

v20.12.2

Reproduction Steps

call:

import {
  type HeadObjectCommandInput,
  S3Client,
  waitUntilObjectExists
} from '@aws-sdk/client-s3';

  const fileParams = {
    Bucket: 'bucket-name',
    Key: 'my-key'
  } satisfies HeadObjectCommandInput;

await waitUntilObjectExists({ 
  client,
  minDelay: 0.5, // exponential backoff floor (seconds)
  maxDelay: 1, // exponential backoff ceiling (seconds)
  maxWaitTime: 30
 }, fileParams);

Observed Behavior

Error: WaiterConfiguration.minDelay must be greater than 0

Expected Behavior

An exponential backoff policy should work, starting with 500ms delay

Possible Solution

No response

Additional Information/Context

No response

[razbensimon]

It's great to see it got fixed! Thanks guys!
on what release it will be available?
@smilkuri / @kuhe

[kuhe]

A fix was released in https://www.npmjs.com/package/@smithy/util-waiter/v/4.0.1.

To use the fix, you will need a version of @aws-sdk/client-s3 that has a ^4.0.0 dependency range and perform a lockfile update or clean install, which is at minimum https://github.com/aws/aws-sdk-js-v3/releases/tag/v3.723.0. This is because all transitive smithy dependencies had major version bumps in the recent release dropping support for Node.js 16 in the AWS SDK for JavaScript v3.

[razbensimon]

Thanks, it workes :)

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.