Set file permissions correctly#338
Merged
philbucher merged 3 commits intomasterfrom Apr 21, 2022
Merged
Conversation
pooyan-dadvand
approved these changes
Mar 31, 2022
Member
pooyan-dadvand
left a comment
pooyan-dadvand
left a comment
There was a problem hiding this comment.
Thanks @philbucher ! It worked for us!
Would you please update the Kratos so @roigcarlo could generate a patch version?
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This should allow that one side uses elevated (i.e. sudo or admin) privileges while the other one does not. I solve this by giving each file that is created equal permissions.
With the proposed solution it works for me on linux, but I cannot reproduce the problem in my Windows setup (regular Win10 with VS2019)