Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Only run eager_load! if config.eager_load is true #1597
With resque 1.27.0+ I've run into a problem where the eager loading change for Rails 4+ is causing
Here is an example stacktrace showing the error:
The "resque-pool" service currently fails to start up except in the Rails "production" environment. This is due to a failure of the "resque" gem to initialise due to a "Cannot define multiple 'included' blocks for a Concern" error. This problem was fixed in the "resque" gem in pull request 1597 (resque/resque#1597), but has not been incorporated into an official gem release yet. This change alters "Gemfile" to depend upon a forked version of the last "1.x" release of the "resque" gem that incorporates the cherry-picked fix for the aforementioned problem. Also included is the "Gemfile.lock" resulting from a "bundle install" resulting from the new "Gemfile" dependencies.