-
Notifications
You must be signed in to change notification settings - Fork 107
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
runtime: Add support for reporting EnclaveRPC peer feedback #4757
Conversation
e48c85b
to
f583c5b
Compare
Codecov Report
@@ Coverage Diff @@
## master #4757 +/- ##
==========================================
+ Coverage 66.55% 66.66% +0.11%
==========================================
Files 446 447 +1
Lines 50031 50065 +34
==========================================
+ Hits 33299 33377 +78
+ Misses 12562 12538 -24
+ Partials 4170 4150 -20
Continue to review full report at Codecov.
|
f583c5b
to
619317b
Compare
This makes EnclaveRPC more robust as the higher-level layer in the runtime can trigger peer replacement on high level errors.
619317b
to
4d28425
Compare
return &protocol.Body{HostRPCCallResponse: &protocol.HostRPCCallResponse{ | ||
Response: cbor.FixSliceForSerde(rsp.Data), | ||
Response: cbor.FixSliceForSerde(rsp), |
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.
Btw is this FixSliceForSerde
still needed? serde
is not used anymore for cbor serialization, right?
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.
True, we could fix it in oasis-cbor, but currently it also doesn't allow deserialization into vectors from NULL, so it is still needed. Will open an issue for it though.
This makes EnclaveRPC more robust as the higher-level layer in the
runtime can trigger peer replacement on high level errors.
TODO
KeyManagerClientWrapper
in the key manager worker.