Closed wlipa closed 5 months ago
Thanks for the report, @wlipa! What version of GoodJob are you using?
good_job (3.29.2)
Unfortunately, I haven't been able to reproduce this yet. Could you share your Gemfile and GoodJob initializer?
Oh, sorry, it looks like I missed the contents of config/good_job.rb
that you shared. I'd suggest following the instructions from the gem by putting your config in config/initializers/good_job.rb
and following the block syntax rather than assigning a hash to config.good_job
.
Sorry, I meant config/initializers/good_job.rb
. Can you explain what you mean about the instructions to follow the block syntax rather than assign a hash, as they both read as valid and supported when I look at the gem instructions?
I meant use the first form of configuration outlined in the gem instructions, where GoodJob settings are done one at a time rather than the second form, where they are done all at once via hash. Regardless, I have created the good-job-config-tweak
branch, which should fix the problem for you, so feel free to try it in your app and let me know how it goes. Assuming it does the job, we can get 5.11.1 released with the fix.
No backtrace when I use that branch, so looks good.
Thanks! 5.11.1 has been released with this fix.
This new backtrace is appearing at app startup with the latest honeybadger gem.
config/good_job.rb: