Mike Perham

Putting it on one line could make it unreadable, no? This logging is primarily meant for localhost development, I've always strongly urged people to use an error service in production....

I really don't want to choose between a dozen "advanced, modern" logger gems. Sidekiq already has a few monkeypatches for ::Logger to add things like Context and per-thread log levels;...

The issue is that a LOT of Sidekiq users do this: ```ruby Sidekiq.configure_server do |cfg| cfg.logger = ::Logger.new("/my/logfile.log") end ``` making it hard to wrap. Logging is the #1 thing...

https://github.com/ruby/logger/issues/84

Interesting. Why are you using einhorn without sidekiqswarm?

Ok. I'm not sure what's wrong. I ask because sidekiqswarm has specific code to implement the systemd watchdog for its children and no one else has had a problem with...

`bin/sidekiqswarm` is designed to run under Einhorn within systemd. `bin/sidekiq` assumes it has full control over the process lifecycle. I'd happily accept smarter integration as a PR.

The timeout is global so you can always go to `Sidekiq.default_configuration[:timeout]`. I think your issue is that concurrency is no longer a single value in Sidekiq. There is the concurrency...

The use of a single, global `scheduled` zset is simply one of legacy. That's how it was originally written 10+ years ago before we even had the SCAN commands and...

> can you confirm that sidekiq-pro maintains at most one thread that calls this script? One thread **per process**. You can have many Sidekiq processes, all calling the script concurrently....