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

Fix validator can specify gas limit #14723

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

terencechain
Copy link
Member

fixes #14721

This PR updates the processProposerSettings function to ensure that the gas limit is overridden correctly. If a loaded setting (from a file) is not nil, it takes priority over both the config and the flag

Testing

We verified the implementation using the following scenarios:

Config Flag File Result
30M N/A N/A 30M
30M N/A 32M 32M
31M 31M N/A 31M
30M 31M 32M 32M

All tests passed as expected, confirming the intended behavior

@terencechain terencechain requested a review from a team as a code owner December 13, 2024 20:33
@terencechain terencechain force-pushed the fix-validator-gas-limit branch from 8f877f6 to f7c8ab8 Compare December 13, 2024 20:47
Copy link
Contributor

@saolyn saolyn left a comment

Choose a reason for hiding this comment

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

lgtm

@james-prysm
Copy link
Contributor

please double check if the configs are saved to db by providing a config file, then restarted without the config file ( meaning it started from a saved state) , the flag should override the database's value. I think it's wrong that the file should override the flag, the flag should be removed imo

loadConfig = dbps.ToConsensus()

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.

Cannot set gas limit through validator client
3 participants