numfmt: handle output write errors#12558
Open
cyphercodes wants to merge 2 commits into
Open
Conversation
|
GNU testsuite comparison: |
Contributor
|
Note : the section is comment 0 "Tests " isn't useful :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
numfmtoutput write failures instead of unwrapping them in formatting writers.write error: ...I/O errors with status 1./dev/fullregression test to ensure this does not panic.Tests
cargo test -p uu_numfmtcargo test --no-default-features --features numfmt test_numfmtcargo clippy -p uu_numfmt -- -D warningscargo fmt --all -- --checkgit diff --checkFixes #12551