Charles Oliver Nutter

@ryanfb If that is true, it would be nice if we could figure out what fixed it and backport that to the 9.3 line (which is still being maintained). Thanks...

This appears to be fixed for 9.3.10 with the JNR stuff backported. Puma starts up ok on my M1.

Revisiting this since it came up on the JRuby mailiing list: There's currently no planned resolution because this is a tricky issue to solve. The workaround of using `--add-opens` is...

I think we're going to have to accept this is unlikely to be fixed in 9.3 given the invasiveness of any fix. It's still problematic to fix in 9.4+ but...

JRuby 9.5 is the big modularity push, so rehoming there.

Detargeting; a few of these are not supportable, and some others have their own issues. We'll leave this in place as a record of the bits we have not finished.

Actually most of the remaining items have been implemented or moved to their own issues.

I happened upon this bug report again so I took a closer look. I am really baffled what might have changed in JRuby to cause this. It's a simple `getProperty`...

I think this may be due to the JIT now being able to compile blocks independent of their surrounding method. The property security check here basically tries to walk up...

JRuby 9.2 has the same JIT but cannot compile looping blocks unless the code around it also compiles. There should be no impact from disabling the JIT other than slower...