show iterable state
https://github.com/sidekiq/sidekiq/issues/6537
I like parts of this but the fundamental issue is that this adds a significant amount of network chatter to the Busy and Queue pages. If we are looking at a page of queued jobs which shows 50 jobs, currently that's 1 call to Redis to call LRANGE in paginator.rb. With this change, we're going to make 51 round trips. I think it is worth refactoring to take advantage of pipelining.
Busy is even worse because large users might have hundreds of jobs running concurrently.
but the fundamental issue is that this adds a significant amount of network chatter to the Busy and Queue pages
I wonder if it is really needed on Busy and Queue pages? Imo, having it on a details page would be enough.
I think it would be fine to add to the job details page.