-
Notifications
You must be signed in to change notification settings - Fork 385
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: TestMaxBlockSize flake #3089
Conversation
The test passes but the app version in test node differs from the one in the block height. ``` app version 0 block header 0 app version 0 block header 2 app version 0 block header 0 app version 0 block header 2 ```
None of these CodeRabbit comments are helpful b/c |
So was app version returning 0 or 2? |
@@ -19,6 +19,6 @@ func (app *App) GovSquareSizeUpperBound(ctx sdk.Context) int { | |||
} | |||
|
|||
gmax := int(app.BlobKeeper.GovMaxSquareSize(ctx)) | |||
hardMax := appconsts.SquareSizeUpperBound(app.AppVersion(ctx)) | |||
hardMax := appconsts.SquareSizeUpperBound(ctx.BlockHeader().Version.App) |
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.
Actually I don't get how this fixes it? The above fix using appVersion should work.
AppVersion calls the consensus parameters which includes the correct app version (the one we should rely on) because we don't always have a header in the context to compare with
Closing this for now. We're hoping that the flake resolves after we bump to a celestia-core release with celestiaorg/celestia-core#1202 and another fix for versions (@cmwaters will create an issue for). |
Closes #3086 by reverting #3075
Re-opens #3066