Skip to content

Migrate with old hackatom #2437

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

Merged
merged 2 commits into from
Mar 25, 2025
Merged

Migrate with old hackatom #2437

merged 2 commits into from
Mar 25, 2025

Conversation

webmaster128
Copy link
Member

This is a preparation for #2433. It is a different issues that only popped up during that work.

It makes explicit what we had before too. Only the old style migrate signature was tested in packages/vm/src/calls.rs because the hackatom.was was not recompiled for a long time. In order to ensure a re-compile does not break these tests, we now pin the version of the contract.

packages/vm/testdata/hackatom.wasm is a plain copy of packages/vm/testdata/hackatom_1.3.wasm for now in order to avoid breaking all the test of the tests.

This makes visible that we lack a test for call_migrate_with_info which actually calls the new migrate function. But we can do that later after recompiling hackatom.wasm.

@webmaster128 webmaster128 force-pushed the migrate-with-old-hackatom branch from e36768c to b0f16ae Compare March 24, 2025 21:27
Copy link
Collaborator

@chipshort chipshort left a comment

Choose a reason for hiding this comment

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

LGTM

@webmaster128 webmaster128 merged commit d9f14f8 into main Mar 25, 2025
42 checks passed
@webmaster128 webmaster128 deleted the migrate-with-old-hackatom branch March 25, 2025 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants