🤖 fix: deterministic timestamps for review stories #1061
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reviews were rendering in non-deterministic order because
createReviewdefaulted toDate.now()for timestamps. When multiple calls happened in the same millisecond, the sort became unstable.Added explicit
baseTime + Ntimestamps to affected stories:This fixes chromatic flakes where review order would vary between runs.
Generated with
mux