Skip to content
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

Update spec test to v1.5.0-beta.0 #14788

Merged
merged 1 commit into from
Jan 13, 2025
Merged

Update spec test to v1.5.0-beta.0 #14788

merged 1 commit into from
Jan 13, 2025

Conversation

terencechain
Copy link
Member

No description provided.

@terencechain terencechain requested a review from a team as a code owner January 10, 2025 04:52
@@ -38,6 +38,7 @@ var placeholderFields = []string{
"MAX_BLOB_COMMITMENTS_PER_BLOCK", // Compile time constant on BeaconBlockBodyDeneb.blob_kzg_commitments.
"MAX_BYTES_PER_TRANSACTION", // Used for ssz of EL transactions. Unused in Prysm.
"MAX_EXTRA_DATA_BYTES", // Compile time constant on ExecutionPayload.extra_data.
"MAX_PAYLOAD_SIZE",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this supposed to be here?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we handle this? The field was renamed from GOSSIP_MAX_SIZE to MAX_PAYLOAD_SIZE

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought about this for a while. For background, this change is based on ethereum/consensus-specs#4045. @nisdas is handling this change entirely in his upcoming PR, so I think it makes more sense to let him manage it all at once, it might get messy for him. In this PR, he will need to remove the variable from the placeholder anyway, or the test will fail

@terencechain terencechain force-pushed the spectest-beta-0 branch 6 times, most recently from e2c6275 to 340248d Compare January 13, 2025 17:07
@terencechain terencechain added this pull request to the merge queue Jan 13, 2025
Merged via the queue into develop with commit e5784d0 Jan 13, 2025
15 checks passed
@terencechain terencechain deleted the spectest-beta-0 branch January 13, 2025 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants