You can clone with
HTTPS or Subversion.
I can't get around this issue in production with the new config options in the worker settings.
It only works in development if I put the recommendable gem before sidekiq in the Gemfile, but it doesn't work regardless of the order in production. It seems like the sidekiq helper is being loaded before the initializer is set.
Hm. I think I might just remove the configuration to change the queue name. These queueing libraries make it pretty easy to work with multiple queues anyway.
Fix #67 and bump to 18.104.22.168
Signed-off-by: David Celis <email@example.com>
I don't suppose you'd mind bundling from this github repository quickly to see if it fixes your issue? Before I do another Gem push.
Trying to deal with the dependencies and how to make order not matter, by the way, has been a pain point for me in the past. If there's something with that that isn't working in 22.214.171.124, I'd appreciate knowing about it. And any advice on that would also be appreciated.
Yah. Seems to work fine... I wonder if a better approach to this would be to have the desired worker loaded as part of the config instead of trying to auto-load it. I don't need the queue_name customization but that might be one way to handle it.