Make statusFile globally-writable #37
Open
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
On some storage backend systems, when the statusFile is created, its write permissions were not granted properly. This commit makes it so that the statusFile, upon creation, has permissions changed so that anybody can write to it.
junkaixue
approved these changes
Mar 12, 2021
narendly
force-pushed
the
li-dev/release-3.6.2-1-backup
branch
from
a5f3e48
to
8b16e3e
Compare
andrewchoi5
approved these changes
Jan 11, 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.
On some storage backend systems, when the statusFile is created, its write permissions were not granted properly. This commit makes it so that the statusFile, upon creation, has permissions changed so that anybody can write to it.