You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a method Env::SetAllowNonOwnerAccess that is meant to change the umask settings for files that are opened. By default this method returns NotSupported.
With the introduction of the FileSystem class, there was an additional "SetAllowNonOwnerAccess" method added to the PosixFileSystem (but not the FileSystem class). There is no wiring between the Env and the FileSystem to update the value for owner access, so the value in PosixFileSystem cannot currently be changed (always true).
When it worked, the umask will be 644 or 600 depending on the whether allow non owner access was true or false.
The only test for this feature (in env_test) is disabled, hence no one noticing the issue.
There are several potential solutions to this problem:
Eliminate the feature altogether (deprecate/remove the API)
Add the corresponding API to the FileSystem class and wire it up accordingly.
Once the FileSystem class is Configurable/Customizable, allow this property to be set through configuration settings.
I will leave it to others to decide if the feature should be deprecated or configurable. Personally, I would prefer #1 or #3 to the adding a new API to the FileSystem class (#2) to support a use case that is likely very specific to one FileSystem implementation.
The text was updated successfully, but these errors were encountered:
This was found during code inspection.
There is a method Env::SetAllowNonOwnerAccess that is meant to change the umask settings for files that are opened. By default this method returns NotSupported.
With the introduction of the FileSystem class, there was an additional "SetAllowNonOwnerAccess" method added to the PosixFileSystem (but not the FileSystem class). There is no wiring between the Env and the FileSystem to update the value for owner access, so the value in PosixFileSystem cannot currently be changed (always true).
When it worked, the umask will be 644 or 600 depending on the whether allow non owner access was true or false.
The only test for this feature (in env_test) is disabled, hence no one noticing the issue.
There are several potential solutions to this problem:
I will leave it to others to decide if the feature should be deprecated or configurable. Personally, I would prefer #1 or #3 to the adding a new API to the FileSystem class (#2) to support a use case that is likely very specific to one FileSystem implementation.
The text was updated successfully, but these errors were encountered: