-
Notifications
You must be signed in to change notification settings - Fork 286
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
refactor(x/signal): reset all versions via ResetTally
#3277
Conversation
Keeping in draft for now. I plan on rebasing after #3290 merges. |
This makes sense to me. I probably intended it to be there but forgot so good find |
ResetTally
ResetTally
WalkthroughThe recent changes involve updating the Changes
Assessment against linked issues
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
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.
LGTM
The only edge case against doing this is imagine we release v2 and shortly after v3 (before the network has upgraded to v2). Some nodes upgrade to v2 and signal v2. Some upgrade to v3 and signal v3. v2 eventually receives quorum and the upgrade happens. Now the nodes who signalled v3 have had their "votes" wiped and so they must revote if they want to move to v3
app/ante/fee_checker.go
Outdated
// The purpose of this wrapper is to enable the passing of an additional paramKeeper parameter in | ||
// ante.NewDeductFeeDecorator whilst still satisfying the ante.TxFeeChecker type. | ||
func ValidateTxFeeWrapper(paramKeeper params.Keeper) ante.TxFeeChecker { | ||
return func(ctx sdk.Context, tx sdk.Tx) (sdk.Coins, int64, error) { | ||
return ValidateTxFee(ctx, tx, paramKeeper) | ||
} | ||
} |
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.
👍
I thought about that edge case and I don't think it's possible because these lines. In other words, when the app version is 1, the nodes that try to signal for 3 will hit an Update: I actually confirmed this in a unit test while working on this PR. |
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.
LGTM
Makes sense. I always wasn't sure whether we should allow skip versions or not |
I'm not sure why golangci-lint is failing on prepare environment. Error looks unrelated to this PR. |
I think we can try skipping the pkg cache |
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.
sorry for the delay. lgtm
…3277) Closes celestiaorg#3276 --------- Co-authored-by: Callum Waters <[email protected]>
Closes #3276