-
Notifications
You must be signed in to change notification settings - Fork 106
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
Client node support for hosting runtimes #3653
Conversation
4567b8e
to
11d0093
Compare
Codecov Report
@@ Coverage Diff @@
## master #3653 +/- ##
==========================================
- Coverage 66.78% 66.63% -0.16%
==========================================
Files 391 393 +2
Lines 38138 38258 +120
==========================================
+ Hits 25472 25492 +20
- Misses 9017 9091 +74
- Partials 3649 3675 +26
Continue to review full report at Codecov.
|
57ff8f6
to
8509b23
Compare
c17d9e1
to
b9a4c6b
Compare
|
||
// RichRuntime provides higher-level functions for talking with a runtime. | ||
type RichRuntime interface { | ||
Runtime |
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.
what are the cases where we'll use Runtime instead of RichRuntime?
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 was thinking about that as well. Probably RichRuntime
would mostly be used and it could just be merged into Runtime
. But we also wouldn't want each Runtime
implementation to implement all of these wrappers. Maybe we could just provide a BaseRuntime
with the wrapper implementations?
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.
Okay yeah. I guess since we don't have plans to have a different implementation of CheckTx, all we have to gain that way is the code being more direct.
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.
feel free to split this out
5b174c3
to
80710c8
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.
thanks for the explanations. lg
|
||
// RichRuntime provides higher-level functions for talking with a runtime. | ||
type RichRuntime interface { | ||
Runtime |
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.
feel free to split this out
Since the PVSS random beacon nodes may be ineligible for committee election on first registration if they register after the commit phase. This adds an extra epoch transition to the E2E test.
80710c8
to
f386f83
Compare
TODO