Update wasi-crypto#4612
Conversation
641f9e0 to
d2f0a36
Compare
|
@sunfishcode Can we get some attention on this? |
| [dependencies] | ||
| anyhow = "1.0" | ||
| wasi-crypto = { path = "spec/implementations/hostcalls/rust", version = "0.1.5" } | ||
| wasi-crypto = { git = "https://github.com/WebAssembly/wasi-crypto", rev="fa309ac", features = ["rcrypto"], default-features = false } |
There was a problem hiding this comment.
wasmtime-wasi-crypto is published on crates.io, which I believe requires that all dependencies be published on crates.io. Can you publish this revision to a new crates.io release, and then depend on that?
There was a problem hiding this comment.
A new version has been pushed to crates.io.
| guest_types::PublickeyEncoding::Pem => PublicKeyEncoding::Pem, | ||
| guest_types::PublickeyEncoding::Sec => PublicKeyEncoding::Sec, | ||
| guest_types::PublickeyEncoding::CompressedSec => PublicKeyEncoding::CompressedSec, | ||
| //guest_types::PublickeyEncoding::CompressedSec => PublicKeyEncoding::CompressedSec, |
There was a problem hiding this comment.
Leftover from debugging code?
| //guest_types::PublickeyEncoding::CompressedSec => PublicKeyEncoding::CompressedSec, | ||
| guest_types::PublickeyEncoding::Local => PublicKeyEncoding::Local, | ||
|
|
||
| _ => todo!("From guest_type::PublicKeyEncoding to PublicKeyEncoding"), |
There was a problem hiding this comment.
raw, pkcs8, pem, sec and local are the only possible values. Why is this todo!() required?
There was a problem hiding this comment.
Removed. Previously I was getting errors about unhandled patterns in the match statement, but that seems to be resolved.
cf93a0d to
ac8e09b
Compare
|
@rjzak -- Looking good now! Thanks! Would you mind resolving the conflict so it can be merged? |
|
@jedisct1 |
b44f576 to
e4199eb
Compare
Signed-off-by: Richard Zak <richard@profian.com>
38dabff to
e10bc64
Compare
Signed-off-by: Richard Zak <richard@profian.com>
e10bc64 to
977a14f
Compare
|
@jedisct1 I could use some advice regarding some of the CI errors. A lot of these are not related to wasi-crypto. |
|
I added the nightly requirement for |
|
@rjzak I don't think However, the errors about dead code were likely due to the example This has been fixed upstream, so an update to a more recent commit should fix the issues we are seeing here as well. |
|
Nightly was only needed for running the test case for Wasi-Crypto, not for compiling the Wasmtime-Wasi-Crypto module. I'll look at updating the Wasi-Crypto submodule. |
|
Yes, but the test case depends on the Rust example bindings. |
Signed-off-by: Richard Zak <richard@profian.com>
|
I've updated the Wasi-Crypto git submodule, may I have a re-run of CI? @sunfishcode or @jedisct1 Edit: nevermind, CI just decided to run as soon as I made this comment? |
|
Abandoning in favour of future PR against the main branch. |
wasmtime-wasi-cryptomissingsymmetric_state_clone#4610.wasi-cryptoCC: @npmccallum, @sunfishcode