01:21 <aryehhillman> Hi — I've had a really difficult time resolving this error:

01:21 <aryehhillman> `(LoadError) load error: psych -- java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.psych.PsychEmitter

01:21 <aryehhillman> org.jruby.embed.EvalFailedException: (LoadError) load error: psych -- java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.psych.PsychEmitter`

01:22 <aryehhillman> Unfortunately I don't have a simple repro but have a few observations:

01:22 <aryehhillman> I am running JRubv 1.9.17 and when I run `irb` and set `GEM_PATH` on the command line and run `require 'psych'` things are great

01:23 <aryehhillman> When I add JRuby to a gradle file and use `runScriptlet` with `require 'pscyh'` (being sure to set GEM_HOME in the script just like from irb) I get the error aboe.

01:23 <aryehhillman> * above.

01:24 <aryehhillman> It doesn't look so much like a Ruby issue, per sé, as an issue with setting up environment that I'm not doing right.

01:24 <aryehhillman> If anyone has any guidance, please let me know... I'll check back later in case any one might have any ideas of how to debug.

01:25 <aryehhillman> Only mentioning the `GEM_HOME` thing as to show that `psych` is being `required` using the same search paths as IRB (i.e. same version)

02:54 <jeremyevans> headius[m]: Weird, last Sequel test on jruby-head (4 days ago) passed: https://travis-ci.org/github/jeremyevans/sequel/jobs/678220350

02:56 <jeremyevans> headius[m]: I haven't seen the failure you posted, and I'm not sure what could cause it.

04:57 <headius[m]> Probably just a glitch then

04:57 <headius[m]> jeremyevans thanks!

21:24 <headius[m]> I may have cracked the module warning nut

21:24 <headius[m]> https://gist.github.com/headius/41d0c8c3a054a0ae2151c4d36c8f6945

21:25 <headius[m]> enebo: that's a template for how we can do access to these packages without triggering warnings

21:25 <headius[m]> have a look

21:25 <headius[m]> The key there is that all the core Java packages always appear to be open to the unnamed module (normal classpath) but they will still warn if you access them. I discovered that if we explicitly addOpens the warning goes away

21:26 <headius[m]> addOpens will fail if it's not actually open so that's where we fall back

23:54 <headius[m]> kares: you probably are interested in this too

23:54 <headius[m]> I have made a PR

23:54 <headius[m]> https://github.com/jruby/jruby/pull/6195

23:54 <headius[m]> I am generifying some of the logic so we can use it for other places where we access JDK internals

23:54 <headius[m]> this will also apply to Java integration; we should not rely on isOpen to know if we can access stuff since it lies