Skip to content

Conversation

@teskje
Copy link
Contributor

@teskje teskje commented Nov 16, 2025

This upgrades us from 0.8.x to 0.9.x. A bunch of breaking changes, though mostly just renames.

rand 0.9 depends on getrandom 0.3, which introduces a way to configure the randomness backend, which is useful for deterministic simulation. Unfortunately, we still also depend on getrandom <0.3 due to transitive dependencies.

Motivation

  • This PR updates a dependency.

Tips for reviewer

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@teskje teskje requested review from a team and aljoscha as code owners November 16, 2025 13:59
Copy link
Contributor

@def- def- left a comment

Choose a reason for hiding this comment

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

No concerns from testing side

let row = match output {
TpchView::Supplier => {
let nation = rng.gen_range(0..count_nation);
let nation = rng.random_range(0..count_nation);
Copy link
Member

Choose a reason for hiding this comment

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

It's somewhat important that we generate the same numbers for the same seed. I'm not sure that rand has this property across versions.

If we don't guarantee this, we'd need to make sure to recreate all tpch sources to avoid negative accumulations.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants