Tyler Rhodes
Tyler Rhodes
We've been experiencing similar issues with frozen workers, ever since upgrading to ruby 3.3.0: Versions - ruby: 3.3.0 - resque: 2.6.0 - resque-pool: 0.7.1 - rails: 7.1.3
> However in this case these workers still had active hearbeats and their state was `working`. One of the console commands we ran was `Resque::Worker.all.map { |w| [w.state, Time.now, w.heartbeat,...
Same issue. The only way to get it output was to 1. write some custom logic to capture it in a notification, or 2. disable noice in order to get...