Skip to content
This repository has been archived by the owner on Oct 19, 2024. It is now read-only.

Fix conflicting feature sets #2191

Closed
DaniPopes opened this issue Feb 24, 2023 · 0 comments
Closed

Fix conflicting feature sets #2191

DaniPopes opened this issue Feb 24, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@DaniPopes
Copy link
Collaborator

DaniPopes commented Feb 24, 2023

All failing feature combinations obtained by running cargo hack.

(target_family = "wasm") --all-features fails. Some of the dependencies that cause this, obtained debugging cargo check --target --all-features with cargo tree --all-features:

  • "Unsupported target os for hidapi-rs" -- hidapi-rusb v1.3.2 from coins-ledger v0.7.1 / trezor-client v0.0.7
  • "Socket2 doesn't support the compile target" -- socket2 v0.4.7 from hyper v0.14.23 / tokio v1.24.1 / h2 v0.3.15 / reqwest v0.11.14 / svm-rs v0.2.21
  • "Only features sync,macros,io-util,rt,time are supported on wasm" -- tokio-1.24.1
    • Same for mio v0.8.5 which is enabled by tokio features which are not supported on wasm (net, process, signal...)
  • "unresolved import super::sysrand_chunk" -- ring v0.16.20 from rustls v0.20.8 / hyper-rustls v0.23.2 / reqwest v0.11.14
    • ring doesn't support wasm32-wasi
@DaniPopes DaniPopes added the bug Something isn't working label Feb 24, 2023
@DaniPopes DaniPopes changed the title Fix features Fix conflicting feature sets Feb 25, 2023
@DaniPopes DaniPopes closed this as not planned Won't fix, can't repro, duplicate, stale Jun 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant