Resque v1.27.0 Release Notes

Release Date: 2017-02-08 // over 5 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)