fix: Append hash to generated file names to avoid conflicts on case-insensitive filesystems #9
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
Signed-off-by: Christina Sørensen <[email protected]>
cafkafk
approved these changes
Nov 16, 2023
There was a problem hiding this comment.
Changed it to just use the hash as a name, and tried it out on eza in eza-community/eza#663
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.
The default filesystem on MacOS is case-insensitive but has case preserving file names. If the test generation has arguments that just differ in case a case-insensitive file name conflict may happen. This fix appends a hash to the generated file name to make them unique.
Fixes issue #10