Ben Sheldon [he/him]

Oh! Maybe you only saw the excerpt that GitHub generated for that code in these comments. If you click into it, there's more highlighted that shows the default constants.

I'm glad to hear that it is working, though it's too bad you had such a mystery! ```ruby config.active_job.queue_adapter = :good_job ``` ... _should_ live in the `config/application.rb` (or `config/environments/*.rb`)....

Thanks for the suggestion! Are you thinking it should be part of the table in the readme?

Thanks for reporting! That looks bad. I can look into that unless you have a theory already.

hmmm, I'm having trouble reproducing this. - Does that happen on any link navigation or just when using the tabbed navbar? - Am I correct in assuming that your operating...

Note to self: maybe related https://github.com/twbs/bootstrap/pull/39224

Thanks for opening this issue. My initial thought on it is that it's tricky: GoodJob's polling query is the same query used by all other mechanisms to "fetch and lock...

Thanks for reporting this! It might be simplest just to raise an argument error when cron is parsed in `GoodJob::CronEntry` and keys are not symbols. What do you think of...

Apologies that I have some recency bias, but we have a similar Resque-based system at my day job and it recently caused an incident because the hardcoded max-memory values were...

Yep, by default GoodJob will wait until all jobs finish. This is changeable with the `shutdown_timeout` option: > `shutdown_timeout` (integer) number of seconds to wait for jobs to finish when...