fix leading dashes in log and pid filenames #180
Closed
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
|
Why |
|
Thanks Brian, cherry-picked onto |
|
Just picked Qq on whim. _ is fine and agree better to have 4 char consistency than inconsequential change in randomness. I think having 2^6 - 1 usable chars is a bug in the Latin alphabet, or some sort of 70's Bell Labs prank that spun out of control. |
|
Hahaha, maybe they take pull requests? |
This was referenced Jan 6, 2020
This was referenced Apr 9, 2022
This was referenced Apr 16, 2022
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.
Fix for issue #178,
utile.randomStringwill give you a leading hypen in 1/64 uids and associated filenames.