[paperclip] saving /my-cool-photos/62/original/my_image.jpg
[AWS S3 200 6.778036 0 retries] put_object(:acl=>:public_read,:bucket_name=>"awesome_bucket",
:content_length=>267949,:content_type=>"image/jpeg",
:data=>Paperclip::UploadedFileAdapter: my_image.jpg,
:key=>"my-cool-photos/62/original/my_image.jpg")
(0.8ms) COMMIT
SQL (0.8ms) UPDATE "people" SET photo_processing = 't' WHERE "people"."id" = 62
Redirected to http://mywebsite.dev/people/62
Completed 302 Found in 7021ms (ActiveRecord: 13.1ms)
Review Load (0.6ms) SELECT "people".* FROM "people" WHERE "people"."id" = $1 LIMIT 1 [["id", 62]]
[paperclip] copying /my-cool-photos/62/original/my_image.jpg to
local file /var/folders/14/03xx7l1s2plg2r4_8zhzttjw0000gn/T/974f4cf28e66e597e205812d72a50e9520120531-27884-zairtv
In fact, when I kill my sidekiq process, the photo still uploads (I can see it in my S3 bucket) but photo_processing is set to true. Once sidekiq runs the job, the value just gets set to false.
In my development enivornment, uploads are still blocking and aren't being handled asynchronously. I've got redis and sidekiq started in development.
My stack:
delayed_paperclip (2.7.1) paperclip (4.1.1) sidekiq (3.1.0)
My model:
Log tailing shows processing happening synchronously:
In fact, when I kill my sidekiq process, the photo still uploads (I can see it in my S3 bucket) but
photo_processing
is set to true. Once sidekiq runs the job, the value just gets set to false.