Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update wasmVM to v1.4.0 #4603

Closed

Conversation

faddat
Copy link
Contributor

@faddat faddat commented Sep 8, 2023

Description

WasmVM has updated to a much newer version of wasmer, which should bring greatly improved performance.

This PR updates wasmvm to v1.4.0, which updates wasmer from the v2.0.x series to the v4.0.x series of wasmer.

Commit Message / Changelog Entry

deps: update wasmvm (credit to @misko9 for test fixes)

see the guidelines for commit messages. (view raw markdown for examples)

Attribution

@misko9 made meaningful contributions to this PR that ensured that tests pass. This is the case for all PR's linked to issue #4612


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md).
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards and Go style guide.
  • Wrote unit and integration tests.
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/).
  • Added relevant godoc comments.
  • Provide a commit message to be used for the changelog entry in the PR description for review.
  • Re-reviewed Files changed in the Github PR explorer.
  • Review Codecov Report in the comment section below once CI passes.

@faddat faddat marked this pull request as draft September 8, 2023 20:02
@faddat faddat marked this pull request as ready for review September 9, 2023 16:16
@faddat faddat requested a review from srdtrk as a code owner September 16, 2023 08:00
@faddat faddat changed the title update wasmVM update wasmVM to v1.4.0 Sep 16, 2023
Comment on lines +14 to +17
ADD https://github.com/CosmWasm/wasmvm/releases/download/v1.4.0/libwasmvm_muslc.aarch64.a /lib/libwasmvm_muslc.aarch64.a
ADD https://github.com/CosmWasm/wasmvm/releases/download/v1.4.0/libwasmvm_muslc.x86_64.a /lib/libwasmvm_muslc.x86_64.a
RUN sha256sum /lib/libwasmvm_muslc.aarch64.a | grep 2a72c7062e3c791792b3dab781c815c9a76083a7997ce6f9f2799aaf577f3c25
RUN sha256sum /lib/libwasmvm_muslc.x86_64.a | grep 8ea2e3b5fae83e671da2bb51115adc88591045953f509955ec38dc02ea5a7b94
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like we need to update the modules/light-clients/08-wasm/Dockerfile instead. But there's no harm actually just updating both for now.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hopefully in the call today we'll be able to clean up the dep we currently have on 08-wasm in ibc-go. when that's done, a couple of things will be able to be removed including these changes to the Dockerfile

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we also wouldn't need to get the aarch64 lib? We should only be running actual tests on x86_64 machine.

@colin-axner
Copy link
Contributor

looks like the feature branch got updated when it was bumped to v0.50 https://github.com/cosmos/ibc-go/blob/feat/wasm-clients/modules/light-clients/08-wasm/go.mod#L22, so I think we can close this pr?

@DimitrisJim
Copy link
Contributor

DimitrisJim commented Oct 4, 2023

@colin-axner we still need the bump of the wasmvm static lib. this should be easier to do in a separate PR. Closing this and will open PR bumping wasmvm (#4834). Thanks @faddat!

@DimitrisJim DimitrisJim closed this Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants