3 ms·
Google internally avoids use of ascii files, so the type of error you are suggesting is unlikley. I suspect it was more a case of incorrect error handling in a
by londons_explore 4y ago
Google internally avoids use of ascii files, so the type of error you are suggesting is unlikley.
I suspect it was more a case of incorrect error handling in a loop... Eg.
output = []
try:
for site in sites:
output += process(site)
except:
print("error!")
write_to_file(output)
- jeffbee 4y agoOr it could have just been a recordio file that was being written by something that crashed in the middle of doing it, and the committed offset was at a valid end of record. Really there's 1000 ways for this to happen all of which are going to sound obvious in retrospect but are easy to commit.
- q3k 4y agoEven straight up Proto is vulnerable to this (either with an unlucky crash right between fields being actually written to a file, or when attempting to stream top-level fields).
- deleted 4y ago[deleted]