Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@phunehehe
Copy link

I just had a fun time debugging a weird behavior when using both resque-restriction and resque-loner in the same job. It turned out both plugins use and provide an implementation for a redis_key method, but due to the nature of each plugin, the implementations are not compatible. resque-restriction needs the key to identify a group of jobs, whereas resque-loner needs the key to identify a single job

I think it would be nice if each plugin uses a name that's more specific to itself. What do you think?

This PR is not addressing backward compatibility. If you like the idea maybe we can discuss more. One way is to only release this in a major version upgrade

to avoid clashing in case redis_key is used by something else
an example is resque-restriction
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant