You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using good_job in a team project and the gem was introduced in a PR along with a change in rails config :
config.good_job.execution_mode = :async
This causes max_cache to be different than 0 and therefore it tries to warm_cache upon initialization.
The problem is that I do not have the good_jobs table yet and my rails db:migrate is supposed to create it but it crashes dues to warm_cache failing because the table does not exists.
The text was updated successfully, but these errors were encountered:
The intention is that it will only run GoodJob in async mode running the webserver, which should make any other commands, tasks or interactive console not run GoodJob in async mode.
Hello,
I'm using good_job in a team project and the gem was introduced in a PR along with a change in rails config :
This causes max_cache to be different than 0 and therefore it tries to warm_cache upon initialization.
The problem is that I do not have the
good_jobs
table yet and myrails db:migrate
is supposed to create it but it crashes dues towarm_cache
failing because the table does not exists.The text was updated successfully, but these errors were encountered: