Repository navigation
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
| ts.ucmd() | ||
| .args(&["-s", "--max-depth=1", "deep"]) | ||
| .fails_with_code(1) | ||
| .no_stdout() |
There was a problem hiding this comment.
could check the full message, --max-depth=1?
Merging this PR will improve performance by 4.59%2 warnings
Performance Changes
Tip Curious why performance improved? Comment Comparing Footnotes
|
|
Binary size comparison: |
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.
du -s --max-depth=0 FILEfailed withsummarizing conflicts with --max-depth=0. GNU accepts it, printsdu: warning: summarizing is the same as using --max-depth=0and goes on (this is thedunote at the end of #16646). Any other depth still conflicts with-s.The depth is now validated before the
-scheck, sodu -s --max-depth=abcreportsinvalid maximum depth 'abc'like GNU, instead of the conflict.The new test covers
-s --max-depth=0,-d 0 -s,-s --max-depth=1and-s --max-depth=abc; it fails onmain. I added the warning to the en-US and fr-FR locales.Refs #16646
AI disclosure: written with help from Claude Code.