-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Fix: unmarshalling issue with multisig keys in v0.42.x #10043
Conversation
I have tested this on master and fails too, so it is not specific to 0.42 @aaronc @robert-zaremba @AmauryM |
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.
Let's extend the test.
@@ -380,4 +381,5 @@ func TestAminoUnmarshalJSON(t *testing.T) { | |||
err := cdc.UnmarshalJSON([]byte(pkJSON), &pk) | |||
require.NoError(t, err) | |||
require.Equal(t, uint32(3), pk.(*kmultisig.LegacyAminoPubKey).Threshold) | |||
require.Equal(t, 5, len(pk.(*kmultisig.LegacyAminoPubKey).PubKeys)) |
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.
Could you add a check for the content of individual keys?
Since the bug is in |
Retargetting doesn't work, because your PR is based on a wrong branch. Could you cherry pick your commit in a new branch based on latest master and reset the branch and change the target please? |
also, you should lint the code |
I have created #10061 to target the |
done by #10113 |
Description
Closes: #10042
This fixes the issue outlined in #10042: The
LegacyAminoPubKey
struct fails to correctly unmarshal from JSON.Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change