fix(fetch) continue event

[cirospaciari]

What does this PR do?

Fix: #7428

• Documentation or TypeScript types (it's okay to leave the rest blank in this case)
• Code changes

How did you verify your code works?

Manual tested using s3 and also added a test

[github-actions]

❌ @cirospaciari 5 files with test failures on bun-darwin-aarch64:

• test/cli/run/env.test.ts
• test/cli/run/require-cache.test.ts
• test/js/bun/test/test-test.test.ts
• test/js/node/watch/fs.watchFile.test.ts
• test/js/third_party/postgres/postgres.test.ts

View test output

^{#e5948e5b3c51aaac6b2b02ae2fce30b20081f2fa}

[github-actions]

❌ @cirospaciari 1 files with test failures on linux-x64:

• test/cli/run/env.test.ts

View test output

^{#8c7b2d286b109f63f91ac0d7870440b41f9d7c3c}

[github-actions]

❌ @cirospaciari 1 files with test failures on linux-x64-baseline:

• test/cli/run/env.test.ts

View test output

^{#8c7b2d286b109f63f91ac0d7870440b41f9d7c3c}

[github-actions]

❌ @cirospaciari 9 files with test failures on bun-darwin-x64-baseline:

• test/cli/run/env.test.ts
• test/js/bun/io/bun-write.test.js
• test/js/bun/spawn/spawn-streaming-stdout.test.ts
• test/js/bun/util/which.test.ts
• test/js/node/fs/fs.test.ts
• test/js/node/watch/fs.watchFile.test.ts
• test/js/third_party/webpack/webpack.test.ts
• test/js/web/timers/setTimeout.test.js
• test/js/web/workers/worker.test.ts

View test output

^{#8c7b2d286b109f63f91ac0d7870440b41f9d7c3c}

[github-actions]

❌ @cirospaciari 11 files with test failures on bun-darwin-x64:

• test/cli/run/env.test.ts
• test/js/bun/spawn/spawn-streaming-stdout.test.ts
• test/js/bun/util/filesink.test.ts
• test/js/bun/util/which.test.ts
• test/js/node/fs/fs.test.ts
• test/js/node/watch/fs.watchFile.test.ts
• test/js/node/worker_threads/worker_threads.test.ts
• test/js/third_party/prompts/prompts.test.ts
• test/js/third_party/webpack/webpack.test.ts
• test/js/web/timers/setInterval.test.js
• test/js/web/timers/setTimeout.test.js

View test output

^{#8c7b2d286b109f63f91ac0d7870440b41f9d7c3c}

[asilvas]

Was hoping this was going to make 1.0.16 release since this might resolve the AWS SDK client issues. What's the blocker?

[Jarred-Sumner]

The blocker is that this approach doesn’t actually detect the continue event. It fakes it. It will emit the continue event even when there was no continue sent.

The change needs to be done in the http client to emit a progress event when it receives continue and then propane that through to JS

[cirospaciari]

To resolve this we need duplex streaming on fetch first, so closing in favor of a true solution.