-
Notifications
You must be signed in to change notification settings - Fork 79
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
Add KV RPC services #610
Add KV RPC services #610
Conversation
Refactor Server to handle many async services Add structure for KV RPC services Add KV RPC empty implementations Refactor ServerContextPool to separate start from join
Regenerate gRPC headers and sources Patch KV generated header for Protobuf DELETE issue Log gRPC version in BackEndKv standalone server
Regenerate gRPC headers and sources
Capture gRPC logging in BackEndKv standalone server Register all first RPC requests on the same context [WIP] Track total server-side RPC instances Add peer tracing in server-side RPC services Fix bidirectional streaming call state machine Improve gRPC log messages
Remove temporary hack from CMake file
Codecov Report
@@ Coverage Diff @@
## master #610 +/- ##
==========================================
+ Coverage 81.75% 81.90% +0.14%
==========================================
Files 167 170 +3
Lines 13947 14215 +268
==========================================
+ Hits 11403 11643 +240
- Misses 2544 2572 +28
Continue to review full report at Codecov.
|
Add unit tests
Add check on sanitizer build for gRPC ASAN/TSAN Simplify CompletionRunner unit test
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.
You should consider renaming silkworm::rpc::RpcService: the current naming causes confusion with gRPC Service, which is a well-known concept in the gRPC model, reflected also in generated code, i.e. Service and AsyncService generated classes.
Yes, you're right. Considering that the Service classes act mainly as factories of RPC calls, I'm going to rename |
Register all first RPC requests on all server contexts Fix data race in BackEnd KV test client
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
Add bidirectional-streaming RPC support
Refactor RPC Server to handle many async services
Add structure for KV RPC services
Add KV RPC empty implementations
Refactor ServerContextPool to separate start from join