-
Notifications
You must be signed in to change notification settings - Fork 15
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
Adopt prio
0.14.0
#1673
Adopt prio
0.14.0
#1673
Conversation
I'm pretty sure this will also break |
ac66f60
to
00898ea
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.
Looking good, I have one parameter naming comment on three different APIs
core/src/task.rs
Outdated
#[derivative(Debug(format_with = "bucket_count"))] | ||
buckets: Vec<u64>, | ||
}, | ||
Prio3Histogram { buckets: usize }, |
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 have a slight preference for naming the parameter length
instead of buckets
here, in order to match with what VDAF uses.
@@ -21,7 +21,7 @@ pub enum ApiVdaf { | |||
/// Corresponds to Prio3Count | |||
Count, | |||
Histogram { | |||
buckets: Vec<u64>, | |||
buckets: usize, |
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.
If we rename the parameter to length
in the aggregator API, we'll want to do the same in the control plane API.
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.
We can't get the end to end Prio3Histogram test working until we have a divviup-api that knows about the VDAF-06 representation of histograms (divviup/divviup-api#410), which opens up a can of worms of how divviup-api should deal with aggregators running different Janus versions. Anyway, for now, I disabled the relevant test.
interop_binaries/src/lib.rs
Outdated
@@ -117,7 +117,7 @@ pub enum VdafObject { | |||
length: NumberAsString<usize>, | |||
}, | |||
Prio3Histogram { | |||
buckets: Vec<NumberAsString<u64>>, | |||
buckets: NumberAsString<usize>, |
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 used length
instead of buckets
in divergentdave/draft-dcook-ppm-dap-interop-test-design#41, again to align with https://cfrg.github.io/draft-irtf-cfrg-vdaf/draft-irtf-cfrg-vdaf.html#section-7.4.3-2.
tools/src/bin/collect.rs
Outdated
help_heading = "VDAF Algorithm and Parameters" | ||
)] | ||
buckets: Option<Buckets>, | ||
buckets: Option<usize>, |
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.
If we replace buckets
with length
elsewhere, we could eliminate this flag and simplify a bit.
The bulk of the changes here deal with the change to the representation of `Prio3Histogram`. Since `prio` 0.14.x implements VDAF-06, taking this change will break compatibility with DAP-04. Part of #1669
c5193b2
to
4a01cc8
Compare
I've renamed |
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.
Looks good, just one more arithmetic issue in some transitional code.
Co-authored-by: David Cook <[email protected]>
Co-authored-by: David Cook <[email protected]>
The bulk of the changes here deal with the change to the representation of
Prio3Histogram
. Sinceprio
0.14.x implements VDAF-06, taking this change will break compatibility with DAP-04.Part of #1669