Make gazelle_python_manifest output deterministic #813
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.
When invoking the update rule on
gazelle_python_manifest
the output generated to
gazelle_python.yaml
mapping fileis not deterministic.
This non-determinism causes the test rule for
gazelle_python_manifest
to always fail.
This patch fixes the bug by sorting the keys before writing it to the
mapping file, making the output deterministic
Test Plan: Existing unit tests to verify the output
Fixes #812
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Issue Number: #812
What is the new behavior?
See commit summary
Does this PR introduce a breaking change?
Other information