Upgraded to DJ 4.0.0 and added -1 config.timeout option

[sawyer]

This should address issue #3 and #6.

• Upgraded to DJ 4.0.0.
• Added ability to guarantee a message does not return to queue with the config.timeout = -1 option.
• Removed the broken rails app demo link from README.

[treeder]

Will this no longer work with 3 then?

[sawyer]

It should be fine with > 3.0.0, however I did not test my changes with delayed_job ~3.0.0. The only real change to make the lib work with 4.0.0 was adding a Job.id attribute.

[treeder]

Ok, then it probably shouldn't force 4+ otherwise we leave out all the 3.0 users. Can you change the Gemfile to > 3.0.0?

[sawyer]

Needs more testing, seeing some odd behaviour.

[polmiro]

@sawyer could you explain what issues are you having? I would be happy to investigate some more tests to get this rolled out

[sawyer]

I've been getting very odd behaviour all day - messages coming off the queue without triggering the Job initializer (for instance, no "[init] Delayed::Backend::Ironmq" showing up in the logs.

I'm running a multi-worker test right now pushing ~100 jobs onto the queue at a time, they all appear to get there no problem, and then after a 30s delay start to get pulled by the workers, but 0-3 jobs just seem to disappear without initializing a job.

I've rolled back my -1 timeout change in case that was the culprit but it hasn't made a difference.

Will update when I get to the bottom of it!

[polmiro]

Awesome, thanks! I might eventually test it out as well and see what I find out.

[andreimoment]

@sawyer, @polmiro, has this been resolved? Is it safe to use delayed_job_ironmq with Rails 4 in production environment?

Thank you!