dwifslpreproc: Handle non-ascii data in eddy error outputs #2313
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.
The FSL
eddy
commands sometimes contain a small block of binary data at the end of their outputs. If, when attempting to write those data to a text file in the scratch directory, an encoding operation occurs, such data may yield aUnicodeEncodeError
. This commit changes the output text files to be opened in binary mode, so such an encoding should no longer be applied.(Note that
__str__()
is defined forMRtrixCmdError
as a straight concatenation ofstdout
andstderr
contents, so there shouldn't be anyascii
conversion happening there)