chore: changes moby/stairway#564
Conversation
Consolidated Tests Results 2026-05-19 - 10:20:53Test ResultsDetails
test-reporter: Run #2209
🎉 All tests passed!TestsView All Tests
🍂 No flaky tests in this run. Github Test Reporter by CTRF 💚 🔄 This comment has been updated |
9469e5d to
6b32d44
Compare
| # - (For tfhe only) a resharing of the key generated during DKG | ||
| # - A bunch of decryptons | ||
| # | ||
| # We note that the key generation and the CRS and resahre (when applicable) are checked against a |
There was a problem hiding this comment.
| # We note that the key generation and the CRS and resahre (when applicable) are checked against a | |
| # We note that the key generation and the CRS and reshare (when applicable) are checked against a |
| #[clap(long = "sid")] | ||
| session_id: Option<u128>, | ||
|
|
||
| /// Number of Ciphertexts to decrypt per session (Note the provided ctxt will be copied this many times on the server side) |
There was a problem hiding this comment.
| /// Number of Ciphertexts to decrypt per session (Note the provided ctxt will be copied this many times on the server side) | |
| /// Number of ciphertexts to decrypt per session (Note the provided ctxt will be copied this many times on the server side) |
|
|
||
| /// Optional argument to set the master seed used by the parties. | ||
| /// Parties will then add their party index to the seed. | ||
| /// Sampled at random if nothing is given |
There was a problem hiding this comment.
| /// Sampled at random if nothing is given | |
| /// Sampled at random if not provided. |
| let ctxt_serialized = std::fs::read(params.input_file)?; | ||
| let ctxt: LevelEllCiphertext = bc2wrap::deserialize_unsafe(&ctxt_serialized)?; |
There was a problem hiding this comment.
There was a problem hiding this comment.
Probably not super high priority to enhance this (even more so since once this PR gets in, I'll copy the code to the NIST repo and hopefully never touch it again)
| } | ||
|
|
||
| // NOTE: Integrated here means we are doing both the preprocessing and online phase | ||
| // in the same call. This denotes a bit with how DKG or DDec is done, but makes it easier |
There was a problem hiding this comment.
"denotes"? Do you mean something like "This is a bit like how DKG or DDec do it…"?
There was a problem hiding this comment.
meant to write differs, my bad
| The crate at `core/experiments` is **not** a | ||
| production crate: it is the testing/benchmarking harness that wires the | ||
| `threshold-*` crates together, ships the MPC party and choreographer binaries | ||
| used to drive end-to-end runs, and contains the benchmark suite. This page | ||
| describes how to run those benchmarks in a wide range of configurations. | ||
| For the rest of this page, we assume the user is working under the | ||
| `core/experiments` directory. |
There was a problem hiding this comment.
The text is great. Seems like the line wrapping might be a bit off on the first line though?
|
|
||
| Between each phase it tears the docker containers down via | ||
| `cleanup_docker`, so each cluster starts from a clean slate. | ||
| - `non-threshold-tfhe-bench.sh` — runs the speed and memory non-threshold |
There was a problem hiding this comment.
If we're being pedantic I think that "speed benchmark" is not wholly accurate. Should be "runtime" or "execution time" I think...
There was a problem hiding this comment.
Change speed by execution time everywhere in chore: docfix
Description of changes
Issue ticket number and link
PR Checklist
I attest that all checked items are satisfied. Any deviation is clearly justified above.
chore: ...).TODO(#issue).unwrap/expect/paniconly in tests or for invariant bugs (documented if present).devopslabel + infra notified + infra-team reviewer assigned.!and affected teams notified.Zeroize+ZeroizeOnDropimplemented.unsafe; if unavoidable: minimal, justified, documented, and test/fuzz covered.Dependency Update Questionnaire (only if deps changed or added)
Answer in the
Cargo.tomlnext to the dependency (or here if updating):More details and explanations for the checklist and dependency updates can be found in CONTRIBUTING.md