You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A fix for #241 introduces a new problem where summary information specific to the file processing thread can never be sent to the main thread.
In the fix for #241, the main thread may see an error printing. If it does, then the main thread immediately closes the channel for the associated file. The file-processing thread then sees that the channel is closed and so it returns without having sent Summary information. Currently, there is no quick fix for this.
Do not print after printing error except in debug builds.
This makes for better cooperationg when piped to other programs
like `head` which may suddenly close the pipe.
This does introduce a new Issue #250.
Issue #241
A fix for #241 introduces a new problem where summary information specific to the file processing thread can never be sent to the main thread.
In the fix for #241, the main thread may see an error printing. If it does, then the main thread immediately closes the channel for the associated file. The file-processing thread then sees that the channel is closed and so it returns without having sent Summary information. Currently, there is no quick fix for this.
To Reproduce
Run and pipe to
head
and pass--summary
Here is the same run without
| head -n1
The text was updated successfully, but these errors were encountered: