coreutils
coreutils copied to clipboard
uutils
Cross-platform Rust rewrite of the GNU coreutils
`kill` accepts signal names regardless of the casing: #6217 `timeout` accepts signal names regardless of the casing (this issue): ```console $ cargo run -q --features timeout timeout -s TeRm 0.1...
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68785 This time with a clear error: ``` Step #4 - "build-check-libfuzzer-address-x86_64": INFO: performing bad build checks for /tmp/not-out/tmpqg6qg5wc/fuzz_split Step #4 - "build-check-libfuzzer-address-x86_64": INFO: performing bad build checks for /tmp/not-out/tmpqg6qg5wc/fuzz_wc...
Since #6256, we accept `-c`, and callers think that we actually verify the checksum of some files. However, we always exit with 0, yielding obvious false-positives like this: ```console $...
This code only considers the *first* occurrence of each flag, which leads to no meaningful behavior, because all subsequent flags get ignored. This is demonstrably wrong: ```console $ cargo run...
Hi, this pr tries to fix parent-perm-race gnu test case. this test tries to check the temporary permissions of directories created by cp which might be too permissive under some...
Fixes #6393 Edit1 : I strace-d the whole thing , we seem to use more than 2x amount of read sys calls (will result in more than 100 extra read...
Fixes #6386
Work towards (but definitely does not close): https://github.com/uutils/coreutils/issues/6397 This just reduces the number of strings that are allocated. We're still at 5x the file though. Even though technically, we don't...
Running it over a test file of about 1G in size results in 15G RSS. Problems start with slurping the entire thing upfront, I don't know how it manages to...
