Got job.. and job done, instantly..

[geomic]

I has_attached_file defined on paperclip, which does 4 quite computationally expensive conversions.

If I leave the process_in_background :upload out, then the conversion works fine, and after 30-40 seconds I get my file(s) in the view.

If I add the process_in_background :upload bit, and run resque in verbose mode: VVERBOSE=1 rake resque:work QUEUE='' I get: * [20:33:38 2012-05-16] 9410: got: (Job{paperclip} | DelayedPaperclip::Jobs::Resque | ["Document", 15, "source"]) ** [20:33:38 2012-05-16] 9410: resque-1.20.0: Forked 9719 at 1337196818 ** [20:33:38 2012-05-16] 9719: resque-1.20.0: Processing paperclip since 1337196818 ** [20:33:38 2012-05-16] 9719: done: (Job{paperclip} | DelayedPaperclip::Jobs::Resque | ["Document", 15, "source"]) So, instantly, in less than a second, the job is defined as started.. and complete.

Would anyone know why? Or how I can see the "actual" code running behind, while the resque rake task's running? I tried to audit it with the resque webserver, but all I get is the job appearing and disappearing in an instant - and again without failure.

P.S. I'm pretty sure it worked a couple times initially, and then randomly decided not to. I'm on a Mac, and tried to empty any /var/folders/XX files that may be causing it to, I don't know, think the job's done?!?

[jrgifford]

I'm unable to replicate using my fork. Are you still experiencing this?