Ensuring executable command doesn't point to a directory #73
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
… class but also an actual file (and not a directory)
|
Thanks. Could you please update changelog? |
SergeyKishenin
added a commit
that referenced
this pull request
Apr 29, 2014
Ensuring executable command doesn't point to a directory
SergeyKishenin
added a commit
that referenced
this pull request
Apr 29, 2014
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.
Ensuring executable command is not only executable as per Ruby's File class but also an actual file (and not a directory). My bower:update rake task was failing because it was pointing to the bower directory in one of my exec paths and not to the actual executable file. Turns out File.executable? returns true for directories too if they have the right permissions.