JVM regex loses package context for deferred user-defined Unicode properties
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 46/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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 withUnknown user-defined property name \\p{main::IsEOL}.t/17_progress.talso 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
IsEOLduring 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.
- Lingua principale
- Perl
- Stelle
- 67
- Fork
- 8
- Merge medio
- 5h 12m
- PR unite (30g)
- 131
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di fglock/PerlOnJava
-
area:cpan-port bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
fglock/PerlOnJava#2153 ·
I maintainer di solito rispondono entro 1 giorno
-
area:cpan-port area:parser bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
fglock/PerlOnJava#2137 ·
I maintainer di solito rispondono entro 1 giorno
-
area:backend area:cpan-port area:runtime bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
fglock/PerlOnJava#2071 ·
I maintainer di solito rispondono entro 1 giorno
-
area:runtime documentation enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
fglock/PerlOnJava#1579 ·
I maintainer di solito rispondono entro 1 giorno
-
area:cpan-port bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 62/100
fglock/PerlOnJava#2157 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di fglock/PerlOnJava
Issue simili
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksApertateam-cli
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 93/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
inverse-inc/packetfence#9728 ·
I maintainer di solito rispondono entro 1 giorno
-
fix(char-create): show the real reason a character is refusedForse già presa @baphomello l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno