-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Comment client breaking #5811
Comment client breaking #5811
Conversation
Input file
Compile
Verifying
Encoding
Compiling
Verifying
Encoding
Compare outputs:
|
@@ -48,6 +48,8 @@ balances or a single balance by denom when the `denom` query parameter is presen | |||
* [\#5785](https://github.com/cosmos/cosmos-sdk/issues/5785) JSON strings coerced to valid UTF-8 bytes at JSON marshalling time | |||
are now replaced by human-readable expressions. This change can potentially break compatibility with all those client side tools | |||
that parse log messages. | |||
* (codec) [\#5799](https://github.com/cosmos/cosmos-sdk/pull/5799) Now we favor the use of MarshalBinaryBare instead of LengthPrefixed in all cases that are not needed, |
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.
@jgimeno can we instead state which commands break here. AFAIK, it's only tx encode/decode
.
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.
This is a bit concerning: cosmos/gaia@680bb19#diff-ef04ec516e080b802253864b259addb3L621
Because of the changes in coins serialization, I'd advise to warn the users about the impact of the change instead of mentioning every single affected command (which could potentially be many)
EDIT: nevermind, that's a different thing (#5790)
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.
Plus, @jgimeno I'd advise to revert the changes in keys serialization. That risks to be a very painful issue for the users
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.
Errr what you linked @alessio has nothing to do with serialization. That's a completely orthogonal change and has been stated in the CHANGELOG already.
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.
#5814 we add the comment here. |
Closes: #5748
Description
For contributor use:
docs/
) or specification (x/<module>/spec/
)godoc
comments.Unreleased
section inCHANGELOG.md
Files changed
in the Github PR explorerFor admin use:
WIP
,R4R
,docs
, etc)