Rails no longer accepts ActiveJob queue adapters for new queuing backends into Rails itself; instead, one is supposed to configure the queue adapter by instantiating the class directly. However when this is done Honeybadger will throw an exception at startup because it expects QueueAdapters to have a .to_sym method. I don't think to_sym is documented anywhere as a requirement for an ActiveJob queue adapter.
Rails no longer accepts ActiveJob queue adapters for new queuing backends into Rails itself; instead, one is supposed to configure the queue adapter by instantiating the class directly. However when this is done Honeybadger will throw an exception at startup because it expects QueueAdapters to have a .to_sym method. I don't think to_sym is documented anywhere as a requirement for an ActiveJob queue adapter.
See: https://github.com/rails/rails/pull/32298
initializer:
config.active_job.queue_adapter = MyQueueAdapter.new
lib/my_queue_adapter.rb:
results in: