On breaking changes in transitive dependencies
a story of a change, that broke Sidekiq's reliability promises
Now and then you receive a report about something not working as expected. This time it was scarier than usual: a job, killed by Docker after consuming too much memory with an OOM error, was disappearing from the queue without a trace. In production, we deploy
sidekiq-profor its reliability guarantees, specifically
super_fetchstrategy for pulling work from the queue, and normally should re-queue the job after a restart.