Nested require loses package for helper subs in List::Vectorize
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 52/100
Rechercherichtung
Start by comparing this nested dependency load with the caller/package handling and regression coverage added for #1601. Reproduce with ./jcpan -t Statistics::Multtest, then run the focused ./jperl command from the issue on both JVM and interpreter backends. Add a project owned regression test for the minimal nested load, and confirm the reproducer and all 52 unchanged Statistics-Multtest assertions pass.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Summary
Statistics::Multtest 0.14 fails six assertions in t/1prototype.t on the PerlOnJava JVM backend. Its initial routine calls List::Vectorize::is_array_ref and List::Vectorize::is_hash_ref, but those functions are not present in the expected package after use Statistics::Multtest loads List::Vectorize and its helper files.
The same distribution and dependencies pass under system Perl. This appears related to package context while loading a nested required Perl file without an explicit package declaration, and may be a remaining case in the nested-require caller/package handling addressed by #1601. The small reproducer below fails in the current checkout.
Reproduction
Install Statistics::Multtest 0.14 and its List::Vectorize dependency, then load them through the distribution's normal module path:
./jcpan -t Statistics::Multtest
The failing calls can be isolated after the distributions are installed:
./jperl \
-I<Statistics-Multtest-blib-lib> \
-I<List-Vectorize-blib-lib> \
-e 'use Statistics::Multtest; Statistics::Multtest::initial([0.1])'
On the JVM backend this dies with:
Undefined subroutine &List::Vectorize::is_array_ref called
In List::Vectorize 1.05, is_array_ref is defined in List/Vectorize/lib/Datatype.pl. That file has no package declaration; it is loaded by List::Vectorize.pm using require. With List::Vectorize loaded directly in a top-level one-liner, the symbol is present, but when loaded as a dependency of Statistics::Multtest, it is absent from List::Vectorize's package.
Evidence
- Distribution/version:
Statistics-Multtest0.14; dependencyList-Vectorize1.05. - Archived CPAN run:
20261117-092012-89323. - PerlOnJava JVM backend: 46/52 assertions passed; six failures (tests 1, 3, 5, 7, 9, and 11) in
t/1prototype.t, all failing at the undefinedList::Vectorize::is_array_refcall inStatistics::Multtest::initial. - System Perl oracle from the same run:
Statistics-Multtestpassed all 52 tests;List-Vectorizepassed all 643 dependency tests. - No XS/native dependency is involved.
- The isolated reproducer was run on the JVM backend. Interpreter behavior has not yet been checked.
Expected behavior
Loading List::Vectorize as a dependency should define its helper functions in List::Vectorize, so Statistics::Multtest::initial can validate array and hash references as it does under system Perl.
Related issue
This may be an additional package-context case related to #1601 (nested require caller context). The focused Statistics::Multtest reproducer above still fails in the current checkout and should be compared against the regression coverage added for that issue.
Acceptance criteria
- Add a project-owned regression test for the minimal nested dependency load and validate its expected behavior under system Perl.
- Make the focused reproducer pass on both JVM and interpreter backends.
- Rerun the unchanged
Statistics-Multtest0.14 test suite and confirm all 52 assertions pass.
- Vorherrschende Sprache
- Perl
- Sterne
- 67
- Forks
- 8
- Ø Merge
- 5 Std. 12 Min.
- Gemergte PRs (30 T.)
- 131
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus fglock/PerlOnJava
-
area:cpan-port bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
fglock/PerlOnJava#2153 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:cpan-port area:parser bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
fglock/PerlOnJava#2137 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:backend area:cpan-port area:runtime bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
fglock/PerlOnJava#2071 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:runtime documentation enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
fglock/PerlOnJava#1579 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:cpan-port bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 62/100
fglock/PerlOnJava#2157 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in fglock/PerlOnJava
Ähnliche Issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOffenteam-cli
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 93/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
inverse-inc/packetfence#9728 ·
Maintainer antworten meist innerhalb von 1 Tag
-
fix(char-create): show the real reason a character is refusedEvtl. vergeben @baphomello hat das vor 1 Tag übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag