Fix output data decoding in secretcli q compute tx
#550
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
assafmo
requested review from
Cashmaney,
reuvenpo and
toml01
as code owners
assafmo
changed the title
Cashmaney
approved these changes
Sep 17, 2020
assafmo
changed the title
assafmo
changed the title
secretcli q compute tx
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
secretcli q compute txto correctly decode the output data. In CosmWasm v0.9 the output was wrapped asbase64(hex(data)), now in v0.10 it's wrapped ashex(data).secretcliis now built fromorigin/{current branch}instead oforigin/master.secretclibuild rules.