You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Serialized WASM modules are being created for the embedded wraps; being the reason that it is faster to initialize the WASM Package, hence, improving the dev exp.
We can:
a) Check why the serialized file is modified in the cargo publish process, this would fix situation #1
b) Keep ignoring the files and allow the crates to be pushed with non-committed files, this would fix situation #2
The text was updated successfully, but these errors were encountered:
Serialized WASM modules are being created for the embedded wraps; being the reason that it is faster to initialize the WASM Package, hence, improving the dev exp.
At first, we were committing the files but we got this error: https://github.com/polywrap/rust-client/actions/runs/6036435666/job/16379292848#step:4:2154. Meaning that, when running
cargo publish
it is modifying somehow theserialized
modules; hence, throwing this error.Then, a PR to ignore the
serialized
files was merged #231 and now we're having this error: https://github.com/polywrap/rust-client/actions/runs/6037828180/job/16383805428#step:4:2603. Meaning that, when runningcargo publish
theserialized
files where created but they haven't been committedWe can:
a) Check why the
serialized
file is modified in thecargo publish
process, this would fix situation #1b) Keep ignoring the files and allow the crates to be pushed with non-committed files, this would fix situation #2
The text was updated successfully, but these errors were encountered: