Alexey Zapparov

I've brought back support for pausing queues in main branch, but it's still in alpha. I can backport Sidekiq 7 support from the main branch to v0.X.X

Just re-read the issue. I believe I have massively misinterpreted it at first. The problem comes from the communicator code that I've decided to drop off with no replacement. I...

Will be fixed in 1.0.0 release

I just released v1.0.0.alpha that should work with `sidekiq >= 6.5`. The release is marked as alpha, as I want to add non-breaking changes to global configuration and bring a...

I'm finishing preparation of v1.0.0, which should make this possible. The refactored fetcher class should become compatible with super-fetch out of the box (but I will need volounteers to check...

Just released v1.0.0.alpha that should make sidekiq-throttled compatible with super fetch. But as I don't know hte details of sidekiq-pro, I can't test it myself.

Hmm. I don't really know what is going inside of the register_myself. Without knowing what that method should do, the way I see, would be to provide a mixin for...

> For each capsules, the register_myself will register the capsules as `super_processes` Hmm. So, is should be something like?: ``` ruby def register_myself @config.capsules.each_value do |capsule| capsule.super_process(self) end end ```...

I'm gonna prepare a fix over the next couple of days, but I will need somebody to test it :D

I've changed approach of inheriting from Sidekiq::BasicFetch to directly patching its `#retrieve_work` that should make throttling work on both Sidekiq and Sidekiq::Pro seamingly.