op-node: pipeline deriver wrapper #10962
Merged
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
protolambda
changed the title
protolambda
force-pushed
the
derivation-pipeline-events
branch
from
541c1a8
to
d8b3e70
Compare
protolambda
force-pushed
the
derivation-pipeline-events
branch
from
d8b3e70
to
1846a86
Compare
protolambda
changed the title
rdovgan
pushed a commit
to rdovgan/optimism
that referenced
this pull request
Jun 24, 2024
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
This introduces a wrapper around derivation pipeline (the L1 data -> L2 block attributes conversion process), to step/reset based on events, and return back the status with events.
This does not change the usage of the derivation pipeline in the op-program yet; that can be done together with the other changes in #10947
Tests
Derivation usage is covered in almost every e2e system/action test. The wrapper around the derivation pipeline basically just maps inputs/outputs to pipeline calls to events, little point in unit-testing when it already runs through the same in e2e action tests.
Metadata
Fix #10957