Warning about loading tilt/haml in a non thread-safe way

I’m seeing this warning in my Gradle-based project:

WARN: tilt autoloading 'tilt/haml' in a non thread-safe way; explicit require 'tilt/haml' suggested.

The same warning also shows up in this sample project: https://github.com/JGrenier/asciidoclet-sample

I’m using Gradle 2.6.

[johncarl81]

… perhaps we should upgrade asciidoclet to the latest asciidoctorj as well then.

[enebo]

@johncarl81 for some reason your exec:java is not working for me but if I generate with package in your last changes to pom.xml the shaded jar it generates will run. So both my instincts seem to be right:

java -Djruby.jit.background=false -jar target/asciidoctorj-test-1.0-SNAPSHOT-shaded.jar 
Jul 05, 2018 3:15:23 PM org.asciidoctor.internal.JRubyAsciidoctor render
SEVERE: org.jruby.RubyNoMethodError
Errored after 50 iterations.

I get 50 iterations consistently so what we generate when switching to full build is broken. Also if set threshold to -1 then no full build is performed and all is working:

java -Djruby.jit.threshold=-1 -Djruby.jit.background=false -jar target/asciidoctorj-test-1.0-SNAPSHOT-shaded.jar 

So at this point we know we have a bug in full build (which would also occur in JIT itself if it was enabled) and we know what code is doing it. My cursory examination of code in question in its internal representation actually looks ok so next steps is to see how different it looks for real. Perhaps extracting that snippet by itself was inadequate.