`FileUtils.rm_f` and `FileUtils.rm_rf` should not mask exceptions
In recent times, I've been having issues with these methods because they don't let you know when some issue happened while trying to remove the given folders/files.
IMO most users expect all pre-existing folders/files that are passed to these methods to be actually removed by the methods. Instead, when this happens, errors are silently swallowed and normally the result is that you will get some other issue further down the road, making the problem hard to debug.
The current workaround I'm using is to double check whether the files still exist after the method, and raise a custom error if they do, but I still can't see the original problem, so issues are similarly hard to debug.
This is also a deviation from how
rm -rf and
rm -f work, since these tools finish with a failure exit code when they fail to remove the given files. Given that
fileutils is intended to mimic shell functionality, I think this is just a bug.
I think the intention of the
force flag here is to:
- Don't prompt for confirmation.
- Ignore given arguments that are not files that already exist.
But any issue other than that should not be swallowed, and in general I think the method should succeed if and only if the given list of file names does not exist after the methods are done.
I think this is in line with the following note I get when I run
man rm, but also suggests that this is not the standard behavior of "historical implementations"
The rm utility differs from historical implementations in that the -f option only masks attempts to remove non-existent files instead of masking a large variety of errors.
I implemented this at https://github.com/ruby/fileutils/pull/58, but treating this as a bug. I can also implement a more conservative for approach for users that might be using
FileUtils.rm_f but don't really care if the files are removed or not.
Alternative proposals would be
FileUtils.rm_rf(force: strict), or
FileUtils.strict_rm_rf, but to be honest, if this is considered a breaking change, I would ship it as a new major version, and let users update their code to swallow errors themselves if they need to.
Happy to hear any feedback!
No data to display