[5.2] Fix 'No connector for []' null queue driver bug #11664
Merged
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
Setting the queue configuration `default` to `null` throws an `InvalidArgumentException` since there is not a `null` key in the `connections` configuration. To remain backwards compatible, I added the `null` connection configuration to `QueueManager`. Reference [Issue #11051][1] for more details regarding this bug. [1]: #11051
taylorotwell
added a commit
that referenced
this pull request
Jan 4, 2016
Fix 'No connector for []' null queue driver bug
GrahamCampbell
changed the title
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.
Setting the queue configuration
defaulttonullthrows anInvalidArgumentExceptionsince there is not anullkey in theconnectionsconfiguration.To remain backwards compatible, I added the
nullconnectionconfiguration to
QueueManager.Reference Issue #11051 for more details regarding this bug.