Fix permissions when openrsync is used #2708
Open
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 file permissions when
openrsync
is used on macOS 14.5+.What was changed
Apply write permission using
find
&chmod
when running on macOS 14.5+. To mitigate any previousbazel run
invocations that already left the temporary directory without write permissions, an additional check and call to fix the permissions is added before callingrsync
. This is needed whenrsync
needs to delete or modify any existing files.Why was this changed
macOS 15.4.1 replaced the rsync implementation with openrsync. Apple seems to have added some additional flags like
--chmod
to openrsync to match the functionality and interface of rsync. Unfortunately, not there are bugs like--chmod
being not properly applied when syncing directories.How to test
bazelisk run //examples/ios/HelloWorld --define=apple.experimental.tree_artifact_outputs=1
.simctl
should fail with a permission error. (If this steps succeeds, delete the temporary directory and uninstall HelloWorld from the iOS simulator).