Mike Perham

If the job is enqueued in the default queue, you'd use `redis-cli` like this: > redis-cli lindex queue:default 0 If the job is a retry, you'd need to use a...

The issue is that you haven't shown me how to reproduce the problem. I can create both native Sidekiq::Jobs and ActiveJobs which crash and render fine when I go to...

I've already asked for the job payload. Your initializer would also be helpful.

If you can give me the exact URL of a retry which crashes, I can give you the ZRANGE command to pull out that data.

> redis-cli "zrange" "retry" "1717471278.092402" "1717471278.092402" "BYSCORE" "withscores" Obviously you'll need to add the parameters to connect to your production instance.

If you run `redis-cli monitor` in a local Terminal, you can see the redis commands that Sidekiq runs as you use it on your machine; you can click around the...

Sidekiq::Process should include the capsules, as they show up on the Busy tab.

> Just a small suggestion. The `middlewares` object seems very flexible, but a bit complex maybe 🤔? What about some more high level flag to easily configure the assets paths,...

Here's the latest API from the (great!) feedback so far: ```ruby Sidekiq::Web.register(SidekiqExt::RedisInfo::Web, name: "redis_info", tab: ["Redis"], # The name on your Tab(s) index: ["redis_info"], # The path to the root...

Ok, I'm happy with this PR as is. Any further feedback? cc @mhenrixon