-
Notifications
You must be signed in to change notification settings - Fork 3
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
Consensus failure when manifest.Params
doesn't contain params.Inflation
#61
Comments
Sounds like it just needs a Validate() inflation not nil check ? |
Here's the message I'm getting in the node logs
I'm not sure what the idiomatic fix is but the Happy to get your input. Edit: The issue occurs when I execute the following Group proposal manifestUpdateProposal = &manifesttypes.MsgUpdateParams{
Authority: groupAddr,
Params: manifesttypes.Params{
StakeHolders: []*manifesttypes.StakeHolders{
{
Address: accAddr,
Percentage: 50_000_000,
},
{
Address: acc2Addr,
Percentage: 50_000_000,
},
},
},
} where the Edit2: As you might have guessed, the POA Admin is a Group policy. |
I think Need to look more into & see if instead if we cast a type to not allow it to be nil, thus getting defaults. Worry there is that it would change params to default 0 values, which means the pointer case is ideal to not change others not touched |
Like you said, pointer case is ideal. If the fix is good for you then the case is closed. No need to spend more time on this. |
For the sake of posterity, I had to add the same fix in |
Updating the
manifest
module parameters without supplyingInflation
leads to a consensus failure.The culprit is
in
BeginBlocker
We should add a check.
CC @Reecepbcups
CC @chalabi2
The text was updated successfully, but these errors were encountered: