JVM regex loses package context for deferred user-defined Unicode properties

Abierto
#2,118 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
46/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
backend, testing

Línea de trabajo

Start by tracing RuntimeRegex and UnicodeResolver.activeUserPropertyPackage(), then compare runtime/dynamic regex construction and interpolated regex handling with the interpreter path. Read the existing user_property_package_provenance.t coverage and add a focused regression for Text::ANSI::Fold's deferred IsEOL resolution. Done means the regression passes on system Perl and both PerlOnJava backends, while explicitly qualified properties keep their behavior; confirm the upstream suite passes on the JVM and interpreter.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:backend area:regex bug

Summary

The JVM backend fails to resolve Text-ANSI-Fold's user-defined Unicode property IsEOL in its defining package. The property is defined as Text::ANSI::Fold::IsEOL, but regex execution reports an attempt to resolve main::IsEOL. The same distribution passes under system Perl and PerlOnJava's interpreter backend.

Reproducer

With Text-ANSI-Fold 2.3902 and its declared dependencies installed:

use Text::ANSI::Fold;
print Text::ANSI::Fold->fold("word", width => 10), "\n";

System Perl prints the folded text. On the PerlOnJava JVM backend, the call aborts with:

Unknown user-defined property name \p{main::IsEOL} at Text/ANSI/Fold.pm line 504.

The reported source line is in the folding path; IsEOL is defined in package Text::ANSI::Fold earlier in the module and returns the newline code-point ranges.

Evidence

  • Distribution: Text-ANSI-Fold 2.3902; CPAN run 20261119-133823-51077.
  • The archived JVM run passed t/00_compile.t, then failed across the suite with Unknown user-defined property name \\p{main::IsEOL}. t/17_progress.t also showed dependent assertion failures after property resolution failed.
  • System Perl 5.34.1 passed the complete upstream suite: 18 files, 576 tests.
  • PerlOnJava interpreter passed t/01_fold.t (48 tests). The JVM backend failed the same focused test with the diagnostic above.
  • PerlOnJava source revision used by the archived run: f00b834bab10d59c1dcf802784e05dd4c9726c22 (Perl 5.44.1); OpenJDK 24.0.2 on macOS arm64.

Root-cause direction

The diagnostic shows that the JVM path qualifies the property in main, although the property definition and the regex use belong to Text::ANSI::Fold. RuntimeRegex captures UnicodeResolver.activeUserPropertyPackage() in the compiled regex, and deferred Joni property resolution reinstates that captured package. The run therefore points to a package-provenance loss earlier in the JVM runtime-regex path: by the time the affected regex is compiled or its property context is captured, the package is already main. Trace runtime/dynamic regex construction and interpolated regex handling for this module against the interpreter path, and ensure deferred property resolution uses the regex's defining package.

Existing user_property_package_provenance.t coverage exercises package-local properties and embedding a compiled qr; it does not currently catch this CPAN runtime path.

Acceptance criteria

  • Add a focused project-owned regression that passes on system Perl, fails on the unfixed JVM backend with the package-context error, and passes on both PerlOnJava backends after the fix.
  • Preserve package context for IsEOL during the Text::ANSI::Fold call above, without changing how explicitly qualified properties resolve.
  • Re-run Text-ANSI-Fold 2.3902 on JVM and interpreter and confirm the upstream suite passes.
Lenguaje dominante
Perl
Estrellas
67
Forks
8
Merge medio
5 h 12 min
PR fusionados (30 d)
131

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fglock/PerlOnJava

Todos los issues de fglock/PerlOnJava

Issues similares

Más issues de Perl

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.