YJXRCXOSO2J5BFFR6QKFDVV3RJ5J3QXB4UZ3DVQZLYTF5RJ4TNJAC
OTEE57H2YMEBB2JRHYYAIW4GNXQPV4XEWC4TCI3RXXVU7QTU7TXQC
I know what happened. @finchie, your patch just made the issue even less reproducible, but didn’t solve it.
We were opening a file with OpenOptions
on Unix without truncation, and then directly writing into that file. If the new content was one byte shorter than the previous one, this explains the }}
at the end.
I removed that function since its behaviour on Windows was significantly different from Linux. If truncating is correct on Windows, it should also be correct on Linux.
Ah, good catch! Thanks for the explanation.
I repeated this issue many times and still do not have 100% reproducible steps. Incredible hard to repeat.
Choose
dd
replace bydefault
.Corruption, double
}}
in json file.