Open
Conversation
Collaborator
|
That looks like an invalid config to me. It ought to be a {"queue spec" => count} hash, and nil count indicates an error. We could silently eat the nil and pretend it's a zero (as you did). But I think it's probably better to give a very loud warning or even a fatal error for an invalid config. |
This file contains hidden or 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
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.
Hi,
We've run into a bug here using
resque-pool:I haven't been able to fully understand the issue where here's how the
configobject looks at line312:The function is called for
foo-1so we getniland boom.This PR is a naive fix.. Maybe there's a better way to deal with this issue?