supabase / storage / 38606313469

86%

push

github

fix(tus): bound idle S3 clients separately from the backend (#1509)

## What kind of change does this PR introduce?

Bug fix

## What is the current behavior?

One `STORAGE_S3_CLIENT_TIMEOUT` value is used for both the shared s3
backend and the TUS s3 clients. Unset means 0, which disables the Smithy
socket timeout and an explicit number applies to both.

## What is the new behavior?

Unset means 60 seconds for the TUS s3 clients and 0 for the shared
backend. An explicit value, including 0, still applies to both.

## Additional context

Related to #1478

Signed-off-by: Ferhat Elmas <elmas.ferhat@gmail.com>

7685 of 9476 branches covered (81.1%)

Branch coverage included in aggregate %.

13323 of 15077 relevant lines covered (88.37%)

858.79 hits per line