Ivo Anjo

For what it's worth, I'm using it successfully on Ruby 3.1 + JVM 8. I had to do some minimal changes in my fork ( https://github.com/ivoanjo/s3_website ) but happy camper.

+1 I'm seeing ``` RubyDep: WARNING: Your Ruby may not be supported. RubyDep: WARNING: Your Ruby is: 2.6.2 'truffleruby' (unrecognized). If you need this version supported, please open an issue...

Just to add, I've been able to reproduce this with the following example: ``` ruby require 'redis' require 'redis-lock' $lock_key = 'test_lock_key' redis = Redis.new redis.del("lock:#{$lock_key}") redis.set('counter', 0) threads =...

I don't see any errors getting printed when the threads first get stuck because of a lock that wasn't unlocked. After a while with no thread being able to acquire...

Thanks for tackling this and for the great write-up @headius ! :tada: :rocket:

I'm still alive :) I'm moving so the last few days have been a bit hectic but I'll test and report back ASAP.

Just replied on https://github.com/jruby/jruby/pull/4648#issuecomment-328285522

Thanks for picking this up! I'm still very interested in the use-Java-performance-tooling-to-peek-at-JRuby angle, so I'm anxiously following new developments :)

Yeap, I think being able to use JVM tools easily (or even out of the box), especially in production would be a major value-add.

Really awesome, thanks for the update! :)