Skip to content

Disable ahash runtime-rng to fix wasm build - #68

Open
sebastian-zm wants to merge 1 commit into
cryscan:mainfrom
sebastian-zm:fix-wasm-getrandom
Open

sebastian-zm wants to merge 1 commit into
cryscan:mainfrom
sebastian-zm:fix-wasm-getrandom

Conversation

@sebastian-zm

Copy link
Copy Markdown

ahash 0.8.12's default runtime-rng feature pulls in getrandom 0.3, which refuses to compile for wasm32-unknown-unknown without the getrandom_backend="wasm_js" cfg. Since Cargo.lock is not committed, CI resolves to this version and the wasm-npm job fails. ahash is only used for tokenizer maps, which don't need DoS-resistant random keys, so turn off default features and keep std.

ahash 0.8.12's default `runtime-rng` feature pulls in getrandom 0.3, which
refuses to compile for wasm32-unknown-unknown without the
`getrandom_backend="wasm_js"` cfg. Since Cargo.lock is not committed, CI
resolves to this version and the wasm-npm job fails. ahash is only used
for tokenizer maps, which don't need DoS-resistant random keys, so turn
off default features and keep `std`.
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

Successfully merging this pull request may close these issues.

1 participant