Charles Oliver Nutter

Actually now that I look at it I see this is in the generated "invoker" used as a function pointer to the `MultiRBTree` method `op_aset`. That method has two different...

The bug was introduced early last year when we removed `CompatVersion`, used by `MultiRBTree` to define different methods for 1.8 and 1.9 mode: https://github.com/jruby/jruby/commit/9fa233451423182ac989fd8b60ac4992001b929c In order to detect this situation...

FWIW `CompatVersion` has been deprecated for many years and we had hoped nobody would still be using it... but of course there's old unmaintained gems out there.

I've pushed https://github.com/isaiah/rbtree-jruby/pull/1 to update rbtree-jruby for JRuby 10. There are some changes there that will make it incompatible with JRuby 9.4, but I would prefer to go forward from...

No response from @isaiah on that PR, so I'm not sure if this is going to get merged. If you are depending on this library directly, you may want to...

Can't do much more with this through normal OSS processes, so closing this. Please contact me if you need more direct help addressing this.

Still an issue as of JRuby 9.2.7. I believe this is a flaw in the way we do serialization of Java objects in general; the `marshal_dump`/`marshal_load` mechanism requires us to...

As of JRuby 9.4.7.0 this is still an issue but in a different way. For YAML we try to emit the object as YAML but the result is invalid syntax:...

I can confirm that Ruby 3.1 also just shows the elements, not the index. I believe this is a change in `Enumerator#uniq` logic to handle multiple incoming arguments when only...

There were changes to `Enumerable#map` at some point to pass multiple arguments through differently, either the use of "19" logic for Ruby 1.9, or the juggling of the argument list...