-
Notifications
You must be signed in to change notification settings - Fork 731
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 EngineNewPayloadV4Test unit test #6798
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
We don't need this early check as this is already handled by the
DepositValidator
onAbstractEngineNewPayload
. However, if we do want to have this early check, we would need to modify some tests to support it.IMHO, this comes down to: do we ever have a scenario where GetPayloadV4 is called pre-Prague?
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.
Agree it appears to be a duplicate check. If we are having to validate params for other fields here already then think it makes sense to do it all in one place, rather than spread the check out.
Feels like the domain-level DepositsValidator shouldn't be doing this check if we already have this here
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.
We have shared logic between the different version of
engine_newPayload
implemented onAbstractEngineNewPayload
, because of that we still need the "conditional" validation onAbstractEngineNewPayload
, determined by protocol schedule + DepositsValidator (choosing a validator implementation that makes sense for what fork we are in).When it comes to
EngineNewPayloadV4#validateParameters
, we could enforce checking that the deposits field isn't empty, assuming that we only use V4 after Prague (need to confirm this).Depending on what we think is the correct thing to do, we will need to adjust some of the testing because as of now,
EnginePayloadV4
test extendsEnginePayloadV3
and etc, and a lot of these tests will fail.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.
Ok this method should not be used pre-Prague. I'll adjust a few things.
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.
@jflo might have the most recent context about the best way to migrate to V4.
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.
yeah, this happened a ton on v3 as well, we really need to factor out all the inheritance and replace it with a composition approach.