Mike Perham

Why not just have a new version that only supports 6.5+? Let people use an old version of swk if they want to run an old version of Sidekiq.

Scout APM’s gem breaks Sidekiq 6.5 with this error, see their issue tracker.

Sidekiq::Processor is not a public API nor is sidekiq/util. I take compatibility very seriously for documented, public APIs, deprecate things and document them in major version release notes.

This is something I've always wanted, which is why I asked @davydovanton to save each job runtime in a Redis list, but there's a few gotchas: 1. This feature isn't...

Note I verified that performance_bar is not the cause, it's just plain old glimpse.

The page is not rendering, there's no error aside from our specs not being able to find the expected html markup. We're using capybara-webkit 0.14.1. I don't have the time...

I can't easily use either of those flags because I need the size and modtime for HTTP Content-Length and caching. These are HTTP static assets that I serve with `http.FileServer`.

@kevinburke Neat trick with the conditional build. Forgot about that!

🎉 I'd be happy to provide Sidekiq benchmarks before and after once this lands. Redis driver overhead is a major bottleneck.

Documentation PRs are always welcome. I'd be happy to review.