Skip to content

Fix non-determinism in Reports() - #268

Merged
brunotm merged 2 commits into
masterfrom
nondeterminism-fix-kaleofduty
Sep 15, 2026
Merged

brunotm merged 2 commits into
masterfrom
nondeterminism-fix-kaleofduty

Conversation

@kaleofduty

Copy link
Copy Markdown
Collaborator

Note that this is not necessarily how I would fix this permanently, but it should be a good-enough, highly localized fix for the issue, that should allow us test our hypothesis on staging.

@kaleofduty
kaleofduty requested a review from a team as a code owner September 11, 2026 17:25
@github-actions

Copy link
Copy Markdown
Contributor

👋 kaleofduty, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@kaleofduty kaleofduty changed the title Nondeterminism fix kaleofduty Fix non-determinism in Reports() Sep 11, 2026
@brunotm
brunotm force-pushed the nondeterminism-fix-kaleofduty branch 2 times, most recently from 6364896 to 7f87095 Compare September 14, 2026 16:11
@brunotm
brunotm force-pushed the nondeterminism-fix-kaleofduty branch from 7f87095 to 3624e62 Compare September 15, 2026 06:21
@brunotm
brunotm enabled auto-merge (squash) September 15, 2026 06:21
@brunotm
brunotm merged commit 8f93ea1 into master Sep 15, 2026
15 checks passed
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.

2 participants