bug: S3 checksum is not checked about localstack HOT 12 CLOSED

It works! Thanks!

from localstack.

Thanks for the logs! Seems like a regression has been introduced, I'll fix that shortly.

from localstack.

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

from localstack.

Cool! that was fast, thank you!

is this automatically released when it is merged to master? or when i should expect to have the fix released? thanks!

from localstack.

Thank you for the report! It leads to a nice improvement, so that was great! AWS documentation wasn't too explicit on that point.

The merge to master are pushing the new docker image under the latest tag. You can give it a try by running docker pull localstack/localstack:latest and see if that fixes your issue! If not, please feel free to comment again and I'll re-open the issue. Thank you again!

from localstack.

Just tried with and now all requests get a timeout (30s) before their were working without any problem.

Also, I would change that localstack/localstack:s3-latest hasn’t been updated (it is the version where i do not get the timeouts, but the checksum is not checked)

from localstack.

Right, I'll publish an s3-latest image now and will update you once it's available.

So with the previous regular LocalStack image, did you get timeout before or not?
I'll update you once the image is available.

from localstack.

before i didn’t get any timeout, now i get at every request :(

from localstack.

This does not sound right, is the image properly available? Is it only with S3? Could you share LocalStack logs?
What is the code doing exactly?

I'll publish the S3 image shortly, so you can give it a try too. We've had so hiccup with our pipeline but the image should be available today.

from localstack.

The log:

2024-06-05 16:29:25 
2024-06-05 16:29:25 LocalStack version: 3.4.1.dev
2024-06-05 16:29:25 LocalStack Docker container name: confident_merkle
2024-06-05 16:29:25 LocalStack Docker container id: 3322c9dfb480
2024-06-05 16:29:25 LocalStack Docker image sha: sha256:c1c3449a0e39a458a409d569e803f528b07a4b1351380738767edcc422a3f08a
2024-06-05 16:29:25 LocalStack build date: 2024-06-05
2024-06-05 16:29:25 LocalStack build git hash: c404b137f
2024-06-05 16:29:25 
2024-06-05 16:29:27 2024-06-05T14:29:27.468  INFO --- [  MainThread] localstack.utils.bootstrap : Execution of "start_runtime_components" took 608.40ms
2024-06-05 16:29:27 Ready.
2024-06-05 16:29:32 2024-06-05T14:29:32.766  INFO --- [et.reactor-0] localstack.request.aws     : AWS s3.CreateBucket => 200
2024-06-05 16:29:32 2024-06-05T14:29:32.805  INFO --- [et.reactor-0] localstack.request.aws     : AWS s3.CreateBucket => 200
2024-06-05 16:29:34 2024-06-05T14:29:34.195 ERROR --- [et.reactor-0] l.aws.handlers.logging     : exception during call chain: 'NoneType' object has no attribute 'lower'
2024-06-05 16:29:34 2024-06-05T14:29:34.197  INFO --- [et.reactor-0] localstack.request.aws     : AWS s3.PutObject => 500 (InternalError)
2024-06-05 16:29:37 2024-06-05T14:29:37.009  INFO --- [et.reactor-0] localstack.request.aws     : AWS s3.CreateBucket => 200
2024-06-05 16:29:37 2024-06-05T14:29:37.013  INFO --- [et.reactor-0] localstack.request.aws     : AWS s3.CreateBucket => 200
2024-06-05 16:29:37 2024-06-05T14:29:37.542 ERROR --- [et.reactor-0] l.aws.handlers.logging     : exception during call chain: 'NoneType' object has no attribute 'lower'
2024-06-05 16:29:37 2024-06-05T14:29:37.542  INFO --- [et.reactor-0] localstack.request.aws     : AWS s3.PutObject => 500 (InternalError)

from localstack.

@faltimiras thanks again for the report, the issue you've been having should now be fixed. I've just merged the fix so the new image should be out in around an hour (the localstack/localstack:latest one). I should also publish the s3-latest one as well tomorrow, but you can already try it with the regular image. I'll confirm here once both images are out. Thanks again!

from localstack.

Hello @faltimiras! Both images should now contain the fix. Please tell me if that fixes your issue! Thanks again for the report

from localstack.