-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(cp): continue traversal on NotFound error #10301
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
base: main
Are you sure you want to change the base?
Conversation
|
"Related Issue -> what do you mean? The TODO this PR addresses is in copydir.rs, not in cp.rs. Also since this PR addresses the TODO, can the TODO now be removed? |
|
GNU testsuite comparison: |
Merging this PR will degrade performance by 26.25%
Performance Changes
Comparing Footnotes
|
I apologize, I wrote the file path incorrectly. My mistake. I keep the TODO because I thought you might want to support other error types in the future. If you think no further error support is needed, we can remove the TODO. |
| e, | ||
| "{}", | ||
| translate!( | ||
| "cp-error-cannot-stat-no-such-file", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"cp-error-cannot-stat-no-such-file" is not defined in the translation file. It would need to be added (see truncate as example):
asteba@asteba-MS-7C75:~/dev/coreutils/src/uu$ rg "cannot-stat-no-such-file" .
./cp/src/copydir.rs
326: "cp-error-cannot-stat-no-such-file",
./truncate/locales/fr-FR.ftl
33:truncate-error-cannot-stat-no-such-file = impossible d'obtenir les informations de { $filename } : Aucun fichier ou répertoire de ce type
./truncate/locales/en-US.ftl
33:truncate-error-cannot-stat-no-such-file = cannot stat { $filename }: No such file or directory
./truncate/src/truncate.rs
253: translate!("truncate-error-cannot-stat-no-such-file", "filename" => reference_path.quote()),
| "source" => entry.source_relative.quote() | ||
| ), | ||
| )); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually the TODO and the comment that this function should terminate if there is any kind of error except certain errors seems wrong to me. This does not match the behavior of GNU coreutils and the POSIX specification.
This was added originally in b89e8e5 / #3973
I think the function should continue on any errors to match the behavior of GNU coreutils, or am I missing something?
See the specification:
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/cp.html
""When a failure occurs during the copying of a file hierarchy, cp is required to attempt to copy files that are on the same level in the hierarchy or above the file where the failure occurred. It is unspecified if cp shall attempt to copy files below the file where the failure occurred (which cannot succeed in any case)."
And multiple places in the DESCRIPTION say:
"cp shall write a diagnostic message to standard error, do nothing more with source_file, and go on to any remaining files.""
|
Suggestion: |
|
Also can you please add a test (something like the code below) which triggers the NotFound error? |
Description
This PR addresses a
TODOincopy_direntryregarding error handling during directory traversal.Currently, if a file is missing (e.g., deleted by another process) during a copy operation,
cpterminates immediately. This change allowscpto show a warning and continue with the remaining files when aNotFounderror occurs, consistent with howPermissionDeniedis handled.Changes
io::ErrorKind::NotFoundincopy_direntry.Errearly.Related Issue
Addresses the TODO comment in
src/uu/cp/src/copydir.rs.