-
Notifications
You must be signed in to change notification settings - Fork 268
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
master -> rskip351+rskip144 merge #2755
Merged
Vovchyk
merged 99 commits into
rskip351+rskip144
from
vovchyk/master-rskip351+rskip144-merge
Sep 26, 2024
Merged
master -> rskip351+rskip144 merge #2755
Vovchyk
merged 99 commits into
rskip351+rskip144
from
vovchyk/master-rskip351+rskip144-merge
Sep 26, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…multi_factory feat(smgp): implements eth_call exchange rate provider
Adding new Web Provider
feat(stableMinGasPrice): refactoring
In order to implement the verification of initcode size, necessary for the RSKIP438, we need the constant value with the max allowed value. So we can start to validate and use it on the logic of the verification
In order to have the RIT tests working as we have it today, we need to add triggers for every commit and for when the PR is opened, but only for masters and *-rc branches base branches.
* Initial constants and config for the max initcode size In order to implement the verification of initcode size, necessary for the RSKIP438, we need the constant value with the max allowed value. So we can start to validate and use it on the logic of the verification - Adding scenarios of test for the contract creation with DSL - The validation for the initCode size test was added - The validation is based on the RSKIP that enables it - Validation added for the contractCreation during transaction execution Finished the implementation of transactionCost and initcode size validation - All the logic related with transaction cost was changed to meet the new cost criteria - More tests were added to be sure that the flow is following the RSKIP438 - Tests were added to validate that this cost and validation doesn't impact before reach the activation height Applied some suggestions from review Adding tests to validate the failure if we don't have enough gas to cover initCode * Refactor from the Initcode cost calculation In order to have the exact same logic for the initcode cost calculation, we introduced some new classes that can be easily reused by the TransactionExecutor and VM classes. This way, if this logic change, we won't have to change the code in multiple places. It was also introduced an interface for it, so we can expand this idea and in the future, be able to calculate total transactions just calling a method to calculate it independent of the logic used. * Applying some more suggestions from review Co-Authored-By: Nazaret García Revetria <[email protected]> Co-Authored-By: Vovchyk <[email protected]>
* Initial constants and config for the max initcode size In order to implement the verification of initcode size, necessary for the RSKIP438, we need the constant value with the max allowed value. So we can start to validate and use it on the logic of the verification - Adding scenarios of test for the contract creation with DSL - The validation for the initCode size test was added - The validation is based on the RSKIP that enables it - Validation added for the contractCreation during transaction execution Finished the implementation of transactionCost and initcode size validation - All the logic related with transaction cost was changed to meet the new cost criteria - More tests were added to be sure that the flow is following the RSKIP438 - Tests were added to validate that this cost and validation doesn't impact before reach the activation height Applied some suggestions from review Adding tests to validate the failure if we don't have enough gas to cover initCode * Refactor from the Initcode cost calculation In order to have the exact same logic for the initcode cost calculation, we introduced some new classes that can be easily reused by the TransactionExecutor and VM classes. This way, if this logic change, we won't have to change the code in multiple places. It was also introduced an interface for it, so we can expand this idea and in the future, be able to calculate total transactions just calling a method to calculate it independent of the logic used. * Applying some more suggestions from review Co-Authored-By: Nazaret García Revetria <[email protected]> Co-Authored-By: Vovchyk <[email protected]>
…ksmart/rskj into feature/introduce_initcode_size_limit
…e_limit Initial constants and config for the max initcode size
Co-authored-by: Lucas <[email protected]>
Co-authored-by: Lucas <[email protected]>
Co-authored-by: Lucas <[email protected]>
Co-authored-by: Lucas <[email protected]>
Fixing some issues on RIT workflow
…-fix fix(MaxInitcodeSize): fix NPE in transactionCost() method
build: bump jackson version
chore: increase min supported java version to 17
chore: add java21 support
…p351+rskip144-merge
fmacleal
approved these changes
Sep 25, 2024
Quality Gate passedIssues Measures |
fmacleal
approved these changes
Sep 26, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Motivation and Context
How Has This Been Tested?
Types of changes
Checklist:
fed:rskip351+rskip144