-
Notifications
You must be signed in to change notification settings - Fork 0
chore(consensus): Port Blob Defaults Code #18
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
base: alesforz/feature/blobs
Are you sure you want to change the base?
chore(consensus): Port Blob Defaults Code #18
Conversation
Co-authored-by: Sergio Mena <sergio@informal.systems>
Co-authored-by: Sergio Mena <sergio@informal.systems>
@@ -378,6 +372,7 @@ func TestByzantineConflictingProposalsWithPartition(t *testing.T) { | |||
require.NoError(t, err) | |||
|
|||
conR := NewReactor(css[i], true) // so we don't start the consensus states | |||
conR.conS.state.ConsensusParams.Blob.MaxBytes = types.MaxBlobSizeBytes |
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 might not be needed as here by default the size is not 0, but it does not hurt.
I reverted the commits bumping Go's version, because I think this should be a decision of Berachain's team (and pushed in a separate PR). |
Fix for the `state/indexer/sink/psql` tests failing with a docker port error.
This reverts commit 2fbe78b.
e2e error below. We do enable PBTS in the
|
I found the issue: a sneaky merge added fields to the |
Ran the nightlies. The unit tests of The errors:
|
`manifest.BlobMaxBytesUpdateHeight` < 0. Without this change, if `manifest.BlobMaxBytesUpdateHeight` is -1, `manifest.BlobMaxBytes` would be set to 0, thus making the nightlies fail with a "BlobMaxBytes cannot be 0" error.
No description provided.