Makes permission failures non-fatal when looking for .scalding_repl files#1479
Merged
ianoc merged 1 commit intotwitter:developfrom Jan 21, 2016
Merged
Conversation
Contributor
|
Non $HOME is because you could have more local overrides to the setting in different working paths you invoke the repl from. Or so goes the thinking anyway |
Contributor
|
looks fine to me |
ianoc
added a commit
that referenced
this pull request
Jan 21, 2016
Makes permission failures non-fatal when looking for .scalding_repl files
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
3 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.
It seems that on unixy systems, given the following permission tree structure:
anybody can still read
dir/file. When we're looking for.scalding_replfiles, we don't take this into consideration. Now, instead of failing in this situation, weprintlnthe problem and ignore it.BTW is there a reason we don't use
System.getenv("HOME")here?