| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Codecov Report❌ Patch coverage is 91.66667% with 2 lines in your changes missing coverage. Please review.
@@ Coverage Diff @@
## main #812 +/- ##
==========================================
+ Coverage 92.15% 92.19% +0.03%
==========================================
Files 35 35
Lines 7377 7401 +24
Branches 383 386 +3
==========================================
+ Hits 6798 6823 +25
+ Misses 438 435 -3
- Partials 141 143 +2 ☔ View full report in Codecov by Harness.
|
Sorry, something went wrong.
Merging this PR will not alter performance✅ 20 untouched benchmarks Comparing Xylphy:fix/783-name-wholename-pattern-warnings (262d53e) with main (2a3eac9) |
Sorry, something went wrong.
|
Commit b757e1f has test result changes: bfs testsuite: Test results comparison: Current: TOTAL: 313 / PASSED: 267 / FAILED: 40 / SKIPPED: 6 Reference: TOTAL: 312 / PASSED: 266 / FAILED: 40 / SKIPPED: 6 Changes from main branch: TOTAL: +1 PASSED: +1 FAILED: +0 |
Sorry, something went wrong.
Emit non-fatal warnings at parse time for patterns that can never match,
matching GNU findutils behavior:
- Warn if a -name/-iname pattern contains a directory separator ('/'),
since these predicates match against basenames only.
- Warn if a -path/-wholename/-ipath/-iwholename pattern ends with '/',
since find never constructs paths with a trailing separator.
| Back | FazBrowse Home | New Git URL |
Fixes #783
Summary
This PR implements GNU-compatible warnings for find patterns that can never match anything, addressing issue #783.
Previously, uutils find silently accepted patterns like -name /a.txt or -wholename foo/, which will never produce matches. GNU find emits non-fatal warnings to help users catch these common mistakes early.