-
Notifications
You must be signed in to change notification settings - Fork 411
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
bug: submessages broken when using WithMessageHandler
#1735
Comments
Thank you @Reecepbcups for your bug report! Sub-message handling is a core part of wasmd and any problems are very had to trace on test or production systems. When I took a brief look at the linked Juno version, I could see that not the default wasmd message handler was used but a custom setup is passed to the wasm keeper. Our I would close this issue tomorrow. |
Thank you so much for this! I really appreciate it 😄 I had not considered it being related to the BurnPlugin since that is only Juno specific. Looks like Terp network blindly copy pasted that into their repo which is why it affected them too. |
WithMessageHandler
Thank you for the the insight & examples from both of you, much more clarity on the wasmOpts 👍 |
Bug
Submessages do not work via contract since v0.43.
Juno's Uni testnet has had this with
This did not happen on 0.42.
Codebase: Juno v18.0.0-alpha.3
Terp network has also had this issue (reported in the cosmwasm discord)
Full Error 0.43
Full error 0.45
Reproduce:
(credit to mr_t of Ark protocol for this)
Reported to affect their testnet contracts by:
Request
add a e2e with submessage execution along with the patch
The text was updated successfully, but these errors were encountered: