supabase / storage / 42903078346

88%

push

github

fix(acceptance): poll current content after writes to tolerate CDN invalidation lag (#1690)

## What kind of change does this PR introduce?

Bug fix

## What is the current behavior?

Some versioning acceptance tests read an object's current content, write
to it, then read it again right away. The CDN caches `GET
/object/authenticated/...` and invalidates it asynchronously, so the
second read can return the old body. This flaked in staging
ap-southeast-1:
https://github.com/supabase/storage-acceptance-runner/actions/runs/42855634166

## What is the new behavior?

Those re-reads now poll for the expected content (1s interval, up to
15s) so the CDN cache has time to be invalidated.

## Additional context

N/A

8486 of 10192 branches covered (83.26%)

Branch coverage included in aggregate %.

14511 of 16060 relevant lines covered (90.35%)

1353.7 hits per line