Consistently order rev dep version info - #14246
Merged
Turbo87 merged 1 commit intoJul 16, 2026
Merged
Conversation
Otherwise, postgres doesn't guarantee any order and the test asserting this snapshot can be flaky.
Turbo87
approved these changes
Jul 16, 2026
Turbo87
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Otherwise, postgres doesn't guarantee any order and the test asserting this snapshot can be flaky.
I have a branch locally that changes the schema and somehow changes the undefined order that this snapshot's data gets returned 🤷🏻♀️ it fails consistently without this change and passes consistently with the change.
The versions get associated with the dependencies in the UI based on version ID, so changing the order doesn't change any user-visible behavior.