This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Critical Bug Fix: Use AWS::S3::Object built in download_file method to avoid truncating during #reprocess! #2637
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.
Yesterday, I ran
#reprocess!
and it truncated all original images on S3. The logs show that there was an error processing the image, and then the downloaded image was uploaded again.I inspected the temporary file created from the download, and it was empty, so that explains why the exceptions were thrown and why the original was truncated (Paperclip uploaded the empty image back to S3).
Switching to the AWS::S3::Object built in
download_file
method fixes this.