Stop connecting to an application by default in the console #182
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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