-
Notifications
You must be signed in to change notification settings - Fork 450
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
[Configuration Changes] Execution service 3: initial execution-node, interface+implementation #1537
Conversation
It will be back from execNode's sync_monitor
Conflicts: arbnode/execution/node.go arbnode/maintenance.go arbnode/node.go cmd/nitro/init.go cmd/nitro/nitro.go execution/gethexec/sequencer.go go-ethereum system_tests/arbtrace_test.go system_tests/batch_poster_test.go system_tests/common_test.go system_tests/das_test.go system_tests/forwarder_test.go system_tests/seq_coordinator_test.go system_tests/seqfeed_test.go system_tests/staker_test.go
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.
I haven't reviewed most of the system_tests yet, but here are my comments on everything else. I don't expect to have as much (if any) on the system_tests
execClient = nil | ||
} | ||
if execClient != nil { | ||
err := execClient.Initialize(ctx, n, n.SyncMonitor) |
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.
Could we add Initialize and Start to the interface, or is the SyncMonitor the issue? As-is I'm a bit worried that we might miss this in a refactor and we'd forget to Initialize it.
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.
I don't want to add Initialize to the interface - this is very specific for the gethexec node and would e.g. be very different for a n execution RPC client.
Added Start and StopAndWait, where any client could have a reasonable implementation for these two functions.
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.
Here's the rest of my review, I'm onto the geth side now
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
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
Create (non-async) API for execution client, execution node creates relevant members.
Arbnode still manages execution node, mostly to simplify changes to tests.
pulls in: OffchainLabs/go-ethereum#238