-
Notifications
You must be signed in to change notification settings - Fork 297
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
Starting from transitioned initial anchor with tests #8221
base: master
Are you sure you want to change the base?
Conversation
import tech.pegasys.teku.spec.schemas.SchemaDefinitionsBellatrix; | ||
import tech.pegasys.teku.spec.util.DataStructureUtil; | ||
|
||
class MiscHelpersBellatrixTest { |
Check notice
Code scanning / CodeQL
Unused classes and interfaces Note test
@@ -69,6 +69,7 @@ public void handleRequest(RestApiRequest request) throws JsonProcessingException | |||
request.header(Header.CACHE_CONTROL, CACHE_NONE); | |||
|
|||
final String blockId = request.getPathParameter(PARAMETER_BLOCK_ID); | |||
// FIXME: not sure. Are we ok to return here transitioned state on keyword finalized? |
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.
my understand is that this is ok since this endpoint should mimic the same behaviour as the /eth/v2/debug/beacon/states/{state_id}
but allowing to search for block. We're using the same blockroot for the transitioned state so it looks logical to me that we returned the transitioned state
@@ -375,6 +376,7 @@ private Optional<ReorgContext> computeReorgContext( | |||
return optionalReorgContext; | |||
} | |||
|
|||
// TODO: Test the consequences of having transitioned chainHead |
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.
why would we transition the chainHead? I thought we were only going to transition finalized states/block
PR Description
Based on #7981
Work in progress.
Fixed Issue(s)
Documentation
doc-change-required
label to this PR if updates are required.Changelog