Closed akoshelev closed 3 days ago
Attention: Patch coverage is 98.23789%
with 4 lines
in your changes missing coverage. Please review.
Project coverage is 93.51%. Comparing base (
0cbc5de
) to head (0622515
). Report is 7 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
ipa-core/src/protocol/context/dzkp_malicious.rs | 80.00% | 3 Missing :warning: |
ipa-core/src/protocol/basics/shard_fin.rs | 99.52% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
🚨 Try these New Features:
I made a small change to get rid of Step
associated trait bound and use MaliciousSteps
concrete type. It turns out (thanks sharded shuffle) that it is not possible to provide this type when working with generic contexts, unless we want extra bounds on it.
As we use malicious steps anyway in both implementations, it is just easier to manage this way
for Hybrid protocol we will send all histograms back to the leader shard where they will be aggregated and returned back to the report collector.
For sharded shuffle (test protocol) we will send rows/reports back to the leader to concatenate them all together.
Both of these will be supported by the newly added
ShardAssembledResult
trait, while this PR only brings the implementation for Hybrid