Skip to content

chore: changes moby/stairway#564

Open
titouantanguy wants to merge 61 commits into
mainfrom
titouan/chore/minor-nist-bench
Open

chore: changes moby/stairway#564
titouantanguy wants to merge 61 commits into
mainfrom
titouan/chore/minor-nist-bench

Conversation

@titouantanguy
Copy link
Copy Markdown
Contributor

Description of changes

Issue ticket number and link

PR Checklist

I attest that all checked items are satisfied. Any deviation is clearly justified above.

  • Title follows conventional commits (e.g. chore: ...).
  • Tests added for every new pub item and test coverage has not decreased.
  • Public APIs and non-obvious logic documented; unfinished work marked as TODO(#issue).
  • unwrap/expect/panic only in tests or for invariant bugs (documented if present).
  • No dependency version changes OR (if changed) only minimal required fixes.
  • No architectural protocol changes OR linked spec PR/issue provided.
  • No breaking deployment config changes OR devops label + infra notified + infra-team reviewer assigned.
  • No breaking gRPC / serialized data changes OR commit marked with ! and affected teams notified.
  • No modifications to existing versionized structs OR backward compatibility tests updated.
  • No critical business logic / crypto changes OR ≥2 reviewers assigned.
  • No new sensitive data fields added OR Zeroize + ZeroizeOnDrop implemented.
  • No new public storage data OR data is verifiable (signature / digest).
  • No unsafe; if unavoidable: minimal, justified, documented, and test/fuzz covered.
  • Strongly typed boundaries: typed inputs validated at the edge; no untyped values or errors cross modules.
  • Self-review completed.

Dependency Update Questionnaire (only if deps changed or added)

Answer in the Cargo.toml next to the dependency (or here if updating):

  1. Ownership changes or suspicious concentration?
  2. Low popularity?
  3. Unusual version jump?
  4. Lacking documentation?
  5. Missing CI?
  6. No security / disclosure policy?
  7. Significant size increase?

More details and explanations for the checklist and dependency updates can be found in CONTRIBUTING.md

@cla-bot cla-bot Bot added the cla-signed The CLA has been signed. label May 4, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 4, 2026

Consolidated Tests Results 2026-05-19 - 10:20:53

Test Results

passed 7 passed

Details

tests 7 tests
clock not captured
tool junit-to-ctrf
build build-and-test arrow-right test-reporter link #2209
pull-request chore: changes moby/stairway link #564

test-reporter: Run #2209

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Pending ⏳ Other ❓ Flaky 🍂 Duration ⏱️
7 7 0 0 0 0 0 not captured

🎉 All tests passed!

Tests

View All Tests
Test Name Status Flaky Duration
k8s_test_crs_uniqueness 39.2s
k8s_test_insecure_keygen_encrypt_and_public_decrypt 1m 52s
k8s_test_insecure_keygen_encrypt_multiple_types 2m 5s
k8s_test_keygen_and_crs 1m 51s
k8s_test_keygen_uniqueness 4m 43s
k8s_test_centralized_insecure 52.3s
nightly_full_gen_tests_default_k8s_centralized_sequential_crs 1.6s

🍂 No flaky tests in this run.

Github Test Reporter by CTRF 💚

🔄 This comment has been updated

@titouantanguy titouantanguy marked this pull request as ready for review May 5, 2026 11:15
@titouantanguy titouantanguy requested a review from a team as a code owner May 5, 2026 11:15
@titouantanguy titouantanguy force-pushed the titouan/chore/minor-nist-bench branch from 9469e5d to 6b32d44 Compare May 5, 2026 11:15
@titouantanguy titouantanguy requested a review from a team as a code owner May 11, 2026 15:39
Comment thread docs/guides/threshold-benchmark.md Outdated
Comment thread docs/guides/threshold-benchmark.md Outdated
Comment thread docs/guides/threshold-benchmark.md
Comment thread docs/guides/threshold-benchmark.md
dvdplm
dvdplm previously approved these changes May 18, 2026
Copy link
Copy Markdown
Contributor

@dvdplm dvdplm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, modulo some typos

# - (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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# 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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed in chore: docfix

#[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)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/// 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)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed in chore: docfix


/// 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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/// Sampled at random if nothing is given
/// Sampled at random if not provided.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed in chore: docfix

Comment on lines +355 to +356
let ctxt_serialized = std::fs::read(params.input_file)?;
let ctxt: LevelEllCiphertext = bc2wrap::deserialize_unsafe(&ctxt_serialized)?;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"denotes"? Do you mean something like "This is a bit like how DKG or DDec do it…"?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

meant to write differs, my bad

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed in chore: docfix

Comment thread docs/guides/threshold-benchmark.md Outdated
Comment on lines +20 to +26
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.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The text is great. Seems like the line wrapping might be a bit off on the first line though?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed line wrap in chore: docfix

Comment thread docs/guides/threshold-benchmark.md Outdated

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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're being pedantic I think that "speed benchmark" is not wholly accurate. Should be "runtime" or "execution time" I think...

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change speed by execution time everywhere in chore: docfix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed The CLA has been signed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants