search

ottokruse / s3-spa-upload

Upload a single page application to S3 with the right content-type and cache-control meta-data
22 stars 3 forks source link

SHA mismatch when running #9

Open jamesrusso opened 11 months ago

jamesrusso commented 11 months ago

I am getting a SHA content mismatch when running, not sure why this might be happening. Maybe concurrency issue?

XAmzContentSHA256Mismatch: The provided 'x-amz-content-sha256' header does not match what was computed.

jamesrusso commented 11 months ago

It's also repeatable.

ottokruse commented 11 months ago

Thanks for the report!

This happens all the time or is it incidental? How can it be reproduced?

What version are you using of this lib? And which versions of the AWS SDK? (Run 'npm ls')

jamesrusso commented 11 months ago

I am using latest version since I'm just running npx in GitHub actions. It happened twice in row in one repo and then I set concurrency to 1 and it hasn't happened since. I assume it's something to do with the concurrency option.

I have about 300 files I'm syncing. I'll try and mess around with it and see what else I can figure out.

ottokruse commented 11 months ago

Might it be that the system clock of the box where this run on was off and that caused it? Or there's throttling going on in the GH action. Curious what happens if you set concurrency to e.g. 10 (more than 1 but small enough to not hit any bandwidth/throttling constraints)