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.
In my experience, the CSV logfile frequently gets garbage written to
it. It's unclear to me why that happens: presumably the update script
does that when there's a power outage or suspend or something weird
that frequently happens on laptops.
Instead of trying to figure out how the impossible happens, I figured
it might be better to just deal with it better and silence those
errors. I tried to do this in a better way by using an open hook, but
it's actually quite difficult to do so because compressed handles
don't support customizing the encoding routines the same way io.open
does. Instead we monkeypatch the iterator eventually used by the CSV
parser, which works in my tests.