Last 12 weeks · 65 commits
3 of 6 standards met
Summary Include files modified exactly at the starting timestamp for and its aliases. Starting timestamp is now included; end remains excluded. Added boundary tests and updated help, man page, and changelog. Fixes #2122 Testing All 148 unit tests and direct CLI checks passed. Formatting passed. Clippy passed with existing unused-code warnings suppressed. All 95 integration tests passed, including the new timestamp-boundary regression. AI assistance I used Codex to help develop and test this change. I personally reviewed the work and wrote this PR.
Checks [x] I have read the troubleshooting section and still think this is a bug. Describe the bug you encountered: Hi guys, and thanks for the great fd. However, I believe there's an issue when looking for files created a certain day, when at midnight. Or hour, at start of hour, etc. The compare conditions, now, I believe are changed-after ..... >mtime changed-before .... is missed when you search: what files are created ? Same goes for: what files are created 07:xx, 08:xx?, the files with time 07:00, 08:00 are not found. The lower bound ought to be >= mtime. BR/ Ingemar Describe what you expected to happen: _No response_ What version of are you using? 10.5.0 Which operating system / distribution are you on?
Summary Validate explicit values during CLI argument parsing and reject values outside . Previously, excessively large values could be accepted and later trigger panics or aborts during channel allocation or thread creation. The implicit default remains capped at 64 threads to limit startup overhead, while users on high-core-count systems can explicitly request larger values. Changes use Clap built-in ranged integer validation for accept explicit values from 1 through 65536 retain the separate 64-thread implicit default cap test both accepted and rejected range boundaries document the fix in the changelog Testing (147 passed) the focused Windows integration test is blocked during test-environment setup by OS error 1314 because symlink privileges are unavailable; it fails before reaching the parser assertions Fixes Closes #2078 AI usage OpenCode was used to inspect the review feedback and assist with the implementation and validation of the follow-up change.
Problem The TTY-output sanitizer in escapes all control characters, including (U+000A). This causes multi-line error messages to render as single lines with literal on terminals. Before (broken): After (fixed): Fix In , treat like — both are legitimate whitespace in diagnostic output, not injection vectors. (U+000D) remains escaped because it enables carriage-return output forgery. Test Updated test → to assert that newlines pass through the sanitizer unchanged. Fixes #2104
Repository: sharkdp/fd. Description: A simple, fast and user-friendly alternative to 'find' Stars: 44492, Forks: 1140. Primary language: Rust. Languages: Rust (92.5%), Shell (6.6%), Makefile (0.7%), Awk (0.2%). License: Apache-2.0. Topics: cli, command-line, filesystem, hacktoberfest, regex, rust, search, terminal, tool. Latest release: v10.5.0 (3w ago). Open PRs: 67, open issues: 131. Last activity: 23h ago. Community health: 85%. Top contributors: sharkdp, tmccombs, dependabot[bot], tavianator, reima, alexmaco, jcaplan, marionebl, FallenWarrior2k, mmstick and others.