Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for compatibility with sidekiq >= 6.1.0 #1

Merged
merged 1 commit into from Oct 7, 2020

Conversation

anero
Copy link

@anero anero commented Oct 7, 2020

A refactoring in the internal Fetch API was introduced in Sidekiq 6.1.0 that is not backwards compatible.

As part of this refactoring the object in the :fetch option is expected to be an instance of Sidekiq::BasicFetch or an object that responds to the same methods instead of a Class as it used to be.

This change allows using the gem with newer versions while keeping compatibility with old ones. See sidekiq/sidekiq#4602 for more details.

….0 that is not backwards compatible.

As part of this refactoring the object in the :fetch option is expected
to be an instance of Sidekiq::BasicFetch or an object that responds to
the same methods.

This change allows using the gem with newer versions while keeping
compatibility with old ones. See sidekiq/sidekiq#4602 for more details.
@anero anero added the bug label Oct 7, 2020
@anero anero merged commit 4c85216 into rate-limited-count Oct 7, 2020
@anero anero deleted the fix_for_sidekiq_6_1_0 branch October 7, 2020 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant