Resque v1.27.0 Release Notes
Release Date: 2017-02-08 // about 7 years ago-
π Fixed
- π Fix issue where calling Worker.find, Worker.all, or Worker.working from withing a running job would rewrite the PID file with the PID of the forked worker. This causes a change to the Worker#new API that may affect plugin implementations. See Worker#new and Worker#prepare for details. (@jeremywadsack)
- π· Workers queried out now have the correct hostname (@crazymykl)
- π Fix race condition on worker startup (@stevedomin)
- π² No longer triggers verbose logging if env variables are not set (@ldnunes)
- π» resque/failed/requeue/all when using Redis::Failure::Multiple no longer raises an exception (@ale7714)
- π Improve forking to avoid having a child process escape its code (@dylanahsmith)
- π· Workers now use server time rather than their own time to maintain heartbeats (@fw42)
- π Run eager load hooks for Rails applications versioned 4.x and up (@abhi-patel)
- π Fix bug when encountering an error while pruning workers (Joakim KolsjΓΆ and Tomas Skogberg)
- Children write to PIDFILE immediately after forking, fixing issues when reconnecting to Redis is slow (@fimmtiu)
π Changed
- β‘οΈ Update jQuery from 1.3.2 to 1.12.4 (@chrisccerami)
- No longer user Thread.kill to stop heartbeat (@Sinjo)
β Added
- π· Resque Web UI now prompts for confirmation on clearing failed jobs (Markus Olsen)
- β Adds process status to DirtyExit exception when job is killed via signal (@MishaConway)