alexcrichton commented on Issue #2655:
I think a number of the panic/format-related message warnings were fixed in https://github.com/bytecodealliance/wasmtime/pull/2652, but the other changes look good here! Want to update the
randcrate as well to fix thecargo denyerror?
cfallin commented on Issue #2655:
Ah yes, updated for
cargo-denyas well, thanks!
cfallin commented on Issue #2655:
Hmm, now
cargo-auditis unhappy but it's unclear where the oldrand_coreis coming from -- investigating...
cfallin commented on Issue #2655:
OK, so removing
Cargo.lockand attempting a rebuild runs into some errors inbitvecconflicting withfunty(both have traits that define aBITSassociated constant and there's a resolution conflict). This is getting... exciting. I'm not sure how to proceed generating a freshCargo.lockwithout opening some PRs upstream.If I try to just trim our
Cargo.lockin a more scoped way, I see that the bad versionrand_core 0.5.1is used bywasi-crypto. @sunfishcode or @pchickey, thoughts on this?(Separately, I have some concerns about random CI breakages that require upstream fixes and cause our work to halt -- do we want to talk about whether
cargo-audit/cargo-denyshould be warnings-we-address-ASAP rather than red-CI-errors? Are there compliance reasons they have to be the latter? @tschneidereit thoughts?)
github-actions[bot] commented on Issue #2655:
Subscribe to Label Action
cc @fitzgen
<details>
This issue or pull request has been labeled: "cranelift", "cranelift:area:peepmatic", "cranelift:meta", "cranelift:wasm"Thus the following users have been cc'd because of the following labels:
- fitzgen: cranelift:area:peepmatic
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
cfallin commented on Issue #2655:
Closing as #2656 incorporates these fixes along with fixes for the cargo-audit reports.
Last updated: Dec 13 2025 at 19:03 UTC