telegram-bot-rb
Async job queued but not executed.
I use this bot in async: true mode as Telegram client Everything works fine with ActiveJob default async, requests enqueued and executed. However, if I try to change queue adapter from async to something like solid_queue or sidekiq The enqueued jobs die quietly not executed due this that I find in queue adapter uninitialized constant Telegram::Bot::Client::AsyncJob
If set turn async: false everything start working but currently I can only use this gem in ActiveJobs default async mode
With other adapters you need to start separate processes that process jobs. See sidekiq docs for the command that starts processors.
With other adapters you need to start separate processes that process jobs. See sidekiq docs for the command that starts processors.
Yes I do that. I tried Sidekiq + Redis starting Sidekiq as separate process and Solid Queue.. both have had same result. The job gets enqueued without any fuss and quitey dies. Then I see the error in the adapter's logs. Maybe I miss something important. Once I remove adapter configuration from environment configuration file or make it config.active_job.queue_adapter = :async Everything works fine as it should. It is ok for now, but I wonder if I be able to use other adapters if I need then in the future.
I wil try it on a clean new Rails installation. Maybe there is something in my current project messes it up.