Fix the ID range allocated to Whitney Leach. #2871
Merged
Conversation
This file contains 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
From the very beginning (commit 50200dd), Whitney Leach has been assigned the bogus ID range (4,018,500..4,018,499] -- note how the upper boundary is _lower_ than the lower boundary. The intention was probably to assign the range (4,018,500..4,018,999], which is what we do here. Given that nobody (not even Whitney Leach) has complained about this invalid range for more than 4 years, it is likely that the range is not actually needed, but even if it is unused, a bogus range will prevent the file from being used by tools that actually _validates_ the contents of an ID range policy file.
matentzn
approved these changes
Dec 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
From the very beginning (commit 50200dd), Whitney Leach has been assigned the bogus ID range (4,018,500..4,018,499] -- note how the upper boundary is lower than the lower boundary.
The intention was probably to assign the range (4,018,500..4,018,999], which is what we do here.
Given that nobody (not even Whitney Leach) has complained about this invalid range for more than 4 years, it is likely that the range is not actually needed, but even if it is unused, a bogus range will prevent the file from being used by tools that actually validates the contents of an ID range policy file.