Skip to content
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

aws-config (0.56) depends on tokio+mio - breaks on WASM #2918

Closed
simbleau opened this issue Aug 13, 2023 · 1 comment
Closed

aws-config (0.56) depends on tokio+mio - breaks on WASM #2918

simbleau opened this issue Aug 13, 2023 · 1 comment

Comments

@simbleau
Copy link

mio is not wasm-compatible, which is a dep of tokio.

In the latest version of aws-config (0.56) I believe there was a change, specifically around tls, which started to bring this in.

Here's whats in my toml:

aws-config = { version = "0.56", default-features = false, features = [
  "rustls",
] }

Here's my cargo tree:

├── aws-config v0.56.0
│   ├── aws-credential-types v0.56.0
│   │   ├── aws-smithy-async v0.56.0
│   │   │   ├── futures-util v0.3.28 (*)
│   │   │   ├── pin-project-lite v0.2.12
│   │   │   ├── tokio v1.31.0
│   │   │   │   ├── bytes v1.4.0 (*)
│   │   │   │   ├── libc v0.2.147
│   │   │   │   ├── mio v0.8.8
│   │   │   │   │   └── libc v0.2.147
│   │   │   │   ├── num_cpus v1.16.0
│   │   │   │   │   └── libc v0.2.147

If you try to run a wasm-pack test you'll get this exact heap of errors:
seanmonstar/reqwest#1300

@simbleau
Copy link
Author

I opened this issue in aws-sdk-rust instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant