FIX: Use realpath to determine hard link source #1388
Merged
Conversation
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
satra
added a commit
that referenced
this pull request
Mar 5, 2016
FIX: Use realpath to determine hard link source
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.
Fixes bug introduced in #1161.
Attempting to link to a symlink results in
DataSinkpushing symlinks to the nipype working directory out onto the filesystem at large. Can reproduce by connecting aRenamenode to aDataSinknode.Test verifies the behavior of copying and linking from a symlink, fails prior to fix. Final patch passes optional
copyfilesarguments to secondary calls. That seems like the least surprising behavior.