You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When submitting a Vec<CosmosMsg> for execution on a remote chain, if any of those messages fail:
An error should be returned containing the error for the first message to fail.
State changes for all of the other messages should be rolled back.
To do this, I recommend sending a message in the form [hello {}, bank_send {}], where the first call to hello is on the tester contract, and the second sends more tokens than the proxy owns. Execution for the first message should not add a sender (as added in #1), and the callback should return an error about the bank module.
The text was updated successfully, but these errors were encountered:
// If multiple messages are executed, a single one failing should roll// back all the other messages. This executes three messages:// ```[good, error1, error2]```// Good causes a state change. The expected behavior is that an error// callback is returned containing error1, and the state change is not// applied.funcTestRollback(t*testing.T) {
}
When submitting a
Vec<CosmosMsg>
for execution on a remote chain, if any of those messages fail:To do this, I recommend sending a message in the form
[hello {}, bank_send {}]
, where the first call to hello is on the tester contract, and the second sends more tokens than the proxy owns. Execution for the first message should not add a sender (as added in #1), and the callback should return an error about the bank module.The text was updated successfully, but these errors were encountered: