reader/csv: Use binary mode on Windows #2121
Merged
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.
On windows, when using
open()
, files are opened in Text mode by default. This causes automatic line conversion from\r\n
to\n
. We don't want this behaviour, and furthermore, it messes up our computation. If the file contents areabc\r\n
and Windows is directed to read, it will return 4 bytes,abc\n
. However, the file position as reported bylseek
is 5, since we are five bytes into the file. This means we can miss rows if we get really unlucky with block offsets.Specifying
_O_BINARY
makes windows use binary mode, which is most compatible with the linux behaviour. Our CSV reader is prepared to handle carriage returns anyway.