-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
devnet-sdk: Go in-process backend #14915
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #14915 +/- ##
===========================================
- Coverage 46.19% 42.41% -3.78%
===========================================
Files 1171 1010 -161
Lines 100291 90723 -9568
===========================================
- Hits 46325 38483 -7842
+ Misses 50628 49077 -1551
+ Partials 3338 3163 -175
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
ca5bc88
to
6fe687f
Compare
This PR tracks the Go in-process implementation of the devnet-SDK system now. The devnet-SDK interfaces work is in #14955 (base of this PR) |
3955b2c
to
3457374
Compare
92d0c2a
to
dfb0a2f
Compare
f4e1a96
to
1b9e881
Compare
1b9e881
to
6395172
Compare
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 think the key thing is to work out how to integrate this with the systest acquirer process so that if a kurtosis devnet isn't specified the test just spins up a suitable network. But there seems to be quite a difference in the level of detail tests provide to validate networks and what's required to spin up a new chain with this. I suspect providing defaults would work well but it will be interesting to integrate and see how to make it work in practice.
But I think this looks good generally.
Description
Implements an in-process Go based backend of the devnet-sdk, for faster test iteration / development cycles / efficient CI.
Features:
And composable, so each type of chain / node can be added as desired.
This also adds getter methods to the batcher and proposer services, to retrieve their RPC endpoints.
In separate PRs we'll swap
interopgen
for op-deployer usage (see #15059), and support the op-challenger (see #15057)Tests
Includes a system test, that runs the system, and sees if both L2s reach block 20, as sanity-check.
Additional context
Metadata
Fix #14909