David Genord II
David Genord II
It is probably worth noting somewhere that this is a potentially breaking change. As I noted in #5634, Rails and Devise use a different priority order in what they choose....
You need to whitelist the origin header in CF -> distributions -> behaviors 
Your logs indicated the message was sent, the issue is not within DJ
How are you starting DJ?
The locking system is a lot more complex than simply the `locked_at` column. Usually when people run into multiple workers running jobs at the same time it turns out to...
That looks like some kind of weird connection sharing incident that isn't suppose to happen. DJ automatically disconnects before fork and reconnects after. Maybe you have a thread sneaking in...
I noticed this after I had dug myself out of the weeds. This would have been a better starting point. I did pull your ubuntu release pinning over.
There hasn't been a release because it hasn't been needed. DJ continues to work just fine for the vast majority of users. The only actual issue that I am aware...
Using error handling within ActiveJob prevents errors from propagating to DelayedJob meaning we can't tell it failed and no retry logic within DJ is engaged. DJ error handling can still...