-
Notifications
You must be signed in to change notification settings - Fork 745
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
Conversation
There was a problem hiding this 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
* 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)
* 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") |
There was a problem hiding this comment.
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
New CI test needs to be written to ensure this does not happen again: Write a CI which uploads, and executes/queries a 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 |
wasmd
v0.50.x seems to have a regression that breaks amino signing on execute messages. The issue affects cosmos hub testnets runninggaiad 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: