-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
grunt.file.recurse dies when working in a directory with an Emacs interlock file #1165
Comments
Please post your code. Thanks! |
Hi Vlad. I put a quick demo of the failure up here - https://github.com/iancreditkarma/grunt-file-recurse-fail Just run setup.sh to cause the failure. Looks like grunt.file.recurse is choking on a broken symlink. That probably shouldn't cause a fatal error, right? |
Hi Vlad, I actually have a bit of working code that fixes this issue. I wrap fs.statSync(filepath).isDirectory() in a try/catch block and then write the error to grunt.log.error() Can I put a pull request up for this? |
@iancreditkarma sure, we shall take a look at it |
I'll submit the patch shortly |
Hi Vlad, I created a pull request here - #1170. Let me know if it is up to snuff. |
Emacs uses interlock files to prevent simultaneous editing - https://www.gnu.org/software/emacs/manual/html_node/emacs/Interlocking.html
While recursing over directory containing an interlock file, grunt.file.recurse dies with:
Warning: ENOENT, no such file or directory '' Use --force to continue.
The text was updated successfully, but these errors were encountered: