-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix compiling S3 crate for wasm #3590
Conversation
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
A new generated diff is ready to view.
A new doc preview is ready to view. |
This commit is related to #3590 (comment)
A new generated diff is ready to view.
A new doc preview is ready to view. |
Motivation and Context
Running
cargo build --target wasm32-unknown-unknown --no-default-features
on an S3 crate has stopped working since #3465 with the following error:To address the issue, this PR updates an S3's dependency on
ahash
in a way that disables default features.Testing
Updated the existing test
integration-tests/webassembly
so thatcheck-aws-sdk-standalone-integration-tests
will runcargo check
aws-sdk-s3
against bothwasm32-wasi
andwasm32-unknown-unknown
(the updated check would break if we removeddefault-features = false
from theahash
dependency).Checklist
CHANGELOG.next.toml
if I made changes to the AWS SDK, generated SDK code, or SDK runtime cratesBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.