Closed nicolas-raoul closed 6 years ago
Thanks @olgfok for the pull request!
I think there is still a case where it can fail: When the program is interrupted during decompression. That's probably what happened for the log above. The XML was broken because the downloaded file had not been completely uncompressed.
@nicolas-raoul, thanks for the comment. I think the error from the log happened, because the first time execution was aborted during downloading. If you look at how the file is decompressed, you'll see that it's done in memory by using BZip2CompressorInputStream. So if you interrupt the process during decompression, the compressed file itself remains undamaged and next time execution will decompress the very same file, that was downloaded.
OK thanks for investigating and thanks for the fix! :-)
Steps:
Workaround: Remove all files in the
dumps-cache
folder.The tool should download/extract under a temporary name, and only give the final filename after the extraction finishes (successfully).