CyclopsMC / IntegratedScripting / 33665833901

46%

master-26-lts: 50%

Pull #72

github

Pre-initialize TRegex in the Graal fallback classloader

TRegex resolves its static loggers the first time a regex is compiled.
That lookup validates the "regex" language id against the languages
visible from the thread context classloader, which on a server thread is
NeoForge's classloader that does not see the packaged Graal jars:

  java.lang.IllegalArgumentException: Unknown language or instrument id
  regex, known ids: debugger, engine, graal, sandbox
    at TruffleLogger$LoggerCache.getOrCreateLogger
    at com.oracle.truffle.regex.tregex.util.Loggers.<clinit>
    at com.oracle.truffle.regex.tregex.TRegexCompiler.compile

Because it happens inside a static initializer, the failure is permanent
for the JVM session, and every later script using a regex only reports
"NoClassDefFoundError: Could not initialize class
com.oracle.truffle.regex.tregex.util.Loggers".

Graal 25.0 cached this id set on the logger cache, so it was resolved once
during startup. Since 25.1 it is resolved per call, which is why this only
appeared after the Graal bump.

Compiling a regex during the startup pre-load initializes TRegex while the
context classloader still points to the Graal fallback classloader, where
all other Graal initialization already happens.

Closes #68

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DwXjG9jWXimuecAeHk5oby

276 of 860 branches covered (32.09%)

Branch coverage included in aggregate %.

1316 of 2589 relevant lines covered (50.83%)

22.92 hits per line