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

deps!: use fixed cosmwasm version (v0.51.0) #3230

Merged
merged 14 commits into from
Jul 29, 2024
Merged

Conversation

MSalopek
Copy link
Contributor

@MSalopek MSalopek commented Jul 26, 2024

wasmd v0.50.x seems to have a regression that breaks amino signing on execute messages. The issue affects cosmos hub testnets running gaiad v19.0.0-rc0 - mainnet is unaffected.

It seems that wamd v0.50.x is a broken release that did not get retracted so it can still be imported.
Nothing in the release notes suggested that it was a broken.

Context:

@MSalopek MSalopek marked this pull request as draft July 26, 2024 18:37
@MSalopek MSalopek marked this pull request as ready for review July 26, 2024 21:25
Copy link
Contributor

@p-offtermatt p-offtermatt left a comment

Choose a reason for hiding this comment

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

Tiny nit. LGTM otherwise

@MSalopek MSalopek added A:backport/v21.x state-machine-breaking State machine breaking changes (impacts consensus). dependencies Pull requests that update a dependency file labels Jul 29, 2024
@MSalopek MSalopek merged commit 59574b5 into main Jul 29, 2024
17 checks passed
@MSalopek MSalopek deleted the masa/fix-broken-cosmwasm branch July 29, 2024 11:49
mergify bot pushed a commit that referenced this pull request Jul 29, 2024
* deps!: use fixed cosmwasm version (v0.51.0)

* update build

* update makefile

* update upgrade test with wasmvm version

* update upgrade test with wasmvm version

* update upgrade test with wasmvm version

* update upgrade test with wasmvm version

* fix: handle tests broken by libwasmvm

* update simtests app dir

* appease linter

* update simtests app dir

* appease linter

* apply nits

(cherry picked from commit 59574b5)
MSalopek added a commit that referenced this pull request Jul 29, 2024
* deps!: use fixed cosmwasm version (v0.51.0) (#3230)

* deps!: use fixed cosmwasm version (v0.51.0)

* update build

* update makefile

* update upgrade test with wasmvm version

* update upgrade test with wasmvm version

* update upgrade test with wasmvm version

* update upgrade test with wasmvm version

* fix: handle tests broken by libwasmvm

* update simtests app dir

* appease linter

* update simtests app dir

* appease linter

* apply nits

(cherry picked from commit 59574b5)

* bump changelogs

---------

Co-authored-by: MSalopek <[email protected]>
@@ -469,6 +468,7 @@ func NewAppKeeper(
// Must be called on PFMRouter AFTER TransferKeeper initialized
appKeepers.PFMRouterKeeper.SetTransferKeeper(appKeepers.TransferKeeper)

wasmDir := filepath.Join(homePath, "wasm")
Copy link
Member

@Reecepbcups Reecepbcups Aug 2, 2024

Choose a reason for hiding this comment

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

:(

ref: same issue as I did on Juno: CosmosContracts/juno#961

@Reecepbcups
Copy link
Member

New CI test needs to be written to ensure this does not happen again:

Write a CI which uploads, and executes/queries a contract.
Then upgrade, then try to execute / query again on the SAME contract

This can not be caught if you upload a new contract, since it saved to the new (incorrect) directory. Which is easy to overlook

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A:backport/v21.x dependencies Pull requests that update a dependency file state-machine-breaking State machine breaking changes (impacts consensus).
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants