concurrent-ruby has dropped support for TimerTask timeouts

[ClearlyClaire]

concurrent-ruby 1.1.10 has dropped support for TimerTask timeouts: ruby-concurrency/concurrent-ruby#926

However, TimerTask timeouts are in use in sidekiq-unique-jobs.

This leads to sidekiq regularly outputting the following in the logs, but beyond that, I don't know what are the exact implications:

TimerTask timeouts are now ignored as these were not able to be implemented correctly

[mhenrixon]

Thanks for the report @ClearlyClaire!

I've seen the warnings in one of the projects I am working on. I have some concerns about this since I actually fixed the timeouts to not leak threads so maybe I force a downgrade of concurrent-ruby.

I am afraid that the timeout won't be respected anymore which would really cause problems for people using this gem.