Let Rails eager load the application #1867
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I may be missing something, so please consider this patch a conversation starter :).
When
Rails.application.config.eager_load
is true, Rails already executesamong other things.
You can check this in
main
,7.0
,6.1
,6.0
, ..., all the way back to3.0
(slightly different by then).Therefore, if
config.eager_load
istrue
, not only is this task doing unnecessary work, but it could potentially trigger code execution twice, since idempotence is not a requirement of those hooks.For example, if you test an application with these settings:
you'll see
:CALLED
twice.So, I suspect this might be a leftover from old Resque versions and can be entirely removed.