Ben Sheldon [he/him]

@aried3r thanks for sharing that story about an incident. That's helpful to know these things have consequences. I'll check out Chart.js as an alternative to Chartist. I think I can...

@baka-san interesting. Feel free to open a PR because that would make it easier to talk about the code changes. Could you explain why you would have a job with...

@baka-san you've convinced me to simply make that value accept a proc. Then you could simply make a case statement to match the dynamic key for different values. Sharp knives...

@baka-san I think those values should be dynamically evaluated, rather than stored within the job... to imply that they're a function of the system, rather than the job e.g. keys...

Yep, I don't foresee any problems with your configuration. I would expect GoodJob's migration to pick up the base configuration. GoodJob is not doing anything special with ActiveRecord.

Oh, also thank you for flagging the inconsistency of timestamp vs datetime. They should be functionally equivalent and is just an inconsistent oversight on my part.

@thomasdziedzic I wanted to follow-up. Are you successful in creating GoodJob timestamps with timezones?

@ollym Thanks for flagging this for me. GoodJob is dependent on Concurrent-Ruby for concurrency primitives, so when/if Concurrent Ruby decides to implement Fibers, GoodJob can stand on its shoulders.

@esasse Can you share the setting you're using for `GOOD_JOB_QUEUES=`? If you're using all default values (e.g. `GOOD_JOB_QUEUES=* GOOD_JOB_MAX_THREADS=5`) then the formula there _should_ be the correct one: - One...

@esasse are you seeing this in Development or Production? (it's a little easier to help debug in Development). I want to also say there isn't a downside to over-provisioning the...