This will mess up enqueuing jobs from the console when using multiple adapters because of being in the middle of a migration, and only configuring one of them for Mission Control (eg. migrating from Sidekiq to Solid Queue). It's also not necessary because if we don't have a current server set, we just don't call activating and rely on the queue adapter configured for the job we want to enqueue (which might be per-job or the one set globally as config.active_job.queue_adapter).
This will mess up enqueuing jobs from the console when using multiple adapters because of being in the middle of a migration, and only configuring one of them for Mission Control (eg. migrating from Sidekiq to Solid Queue). It's also not necessary because if we don't have a current server set, we just don't call
activatingand rely on the queue adapter configured for the job we want to enqueue (which might be per-job or the one set globally asconfig.active_job.queue_adapter).Fixes #174