Closed jprendes closed 1 year ago
Hello, I am a code review bot on flows.network. Here are my reviews of code commits in this PR.
Key changes in the patch:
wasmedge-sys
in Cargo.toml
has been changed from 0.17
to 0.17.4
."zstd"
library has been added to the list of dependencies in build.rs
.Potential problems:
wasmedge-sys
is necessary without more context. It would be helpful to understand why the version was specifically changed to 0.17.4
."zstd"
library as a dependency could introduce new issues. It is important to test the static build thoroughly to ensure that all dependencies are linked correctly and that there are no conflicts or compatibility issues with other dependencies.@Mossaka, this should fix the issues in https://github.com/containerd/runwasi/pull/395
@apepkuss Let's tag a new version to ship this on crates.io
@apepkuss Let's tag a new version to ship this on crates.io
Yeah, I'll release a new version. Before that, I'll check the rust-static-lib
workflow first as @jprendes mentioned it's not triggered. Thanks!
@jprendes wasmedge-sdk v0.13.2 and wasmedge-sys v0.17.5 have been released. Please check them out. Thanks!
It looks like upstream WasmEdge has zstd as a new dependency. This is not currently captured in the build script, which results in a linking error when using the
static
feature. This PR also changeswasmedge-sys
minimum requirement from1.7
to1.7.4
sincewasmedge-sdk
is not compatible withwasmedge-sys
1.7.2
(due to theu64
->Duration
change in here)The missing dependency should have been captured by the
rust-static-lib
CI workflow, but it seems that workflow has never been triggered: https://github.com/WasmEdge/wasmedge-rust-sdk/actions/workflows/rust-static-lib.yml This PR makes no attempt at resolving that.