Replacing hard link with symlink for single-file source nodes? #78
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
…some file systems); use symlinkOrCopy instead as in other places
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.
I expect it's rare for hard links to pose an issue, but I'm using AFS which doesn't support hard links across directories (http://www-01.ibm.com/support/docview.wss?uid=swg21047089) so Gobbling a file fails with an EXDEV error. Any chance we could use
symlinkOrCopyinstead oflinkfor single-file source nodes instead? It looks like it's used elsewhere in Gobble and it doesn't seem to break the tests.No hard feelings if you'd rather keep the hard link though!