[CPAN] Object-InsideOut 4.05 fails on JVM with generated exception Fields method
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
Start with t/01-basic.t and the Object::InsideOut::Exception declarations for OIO, OIO::Method, and OIO::Args; reproduce test 39 on both JVM and interpreter backends. Trace the generated Fields method through exception construction and formatting, then add focused project-owned regression coverage. Done means the focused test passes on both backends and the other failing programs and optional prerequisites are investigated.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
Object::InsideOut 4.05 fails its CPAN test suite on PerlOnJava. A focused failure is reproducible only on the JVM backend: t/01-basic.t fails when it catches the expected missing-mandatory-initializer exception. The exception path reports that OIO::Args has no Fields method, even though Object::InsideOut::Exception creates that method dynamically through Exception::Class.
This is a backend compatibility bug in the runtime path for dynamically generated exception classes/methods. The same focused test passes on the interpreter backend and the system-Perl oracle passes the upstream suite. The remaining failing tests below need to be checked for additional causes; this report does not assume they all share the Fields failure.
Evidence
- CPAN random run:
20261111-090841-71684 - Distribution:
Object-InsideOut-4.05 - System Perl: 5.42.2 on macOS 15 / Darwin 25.6.0; CPAN oracle reports all enabled Object::InsideOut tests successful (67 files, 921 tests). Optional
Want-dependent andMath::Random::MT::Auto-dependent tests were skipped because those optional modules were unavailable when Object::InsideOut ran. - PerlOnJava focused reproduction on the same archived distribution: JVM backend fails test 39 of
t/01-basic.twithCan't locate object method "Fields" via package "OIO::Args" at (eval 7) line 13; interpreter backend passes all 39 tests. - PerlOnJava archive run: 27/833 subtests failed in 16/67 test programs. Failing programs:
t/01-basic.t,t/01a-basic.t,t/04-shared.t,t/04a-shared.t,t/05a-require.t,t/08-access.t,t/19-storable.t,t/25-access.t,t/27-exception.t,t/28-lvalue.t,t/29-non_lvalue.t,t/30-all.t,t/42-sh_obj.t,t/43-overload.t,t/47-sh_reuse.t, andt/51-readonly.t. - The archived test run used the repository launcher; the focused comparison was made with the JVM and interpreter backends on the same test. Source checkout at investigation:
3614619c275bd34bcdfb8700be8e31ee3f85a308; Temurin OpenJDK 24.0.2, macOS arm64.
Expected behavior
The JVM backend should be able to call Fields on dynamically generated Exception::Class subclasses just as the interpreter backend and system Perl do. t/01-basic.t should catch the intended OIO::Args exception and pass its missing-initializer assertion.
Actual behavior
The JVM run fails while constructing or formatting the exception, replacing the intended exception with a missing-method error for OIO::Args::Fields. The interpreter passes that test. This makes the issue reproducible without relying on the larger set of unrelated suite failures.
Investigation notes
Object::InsideOut::Exception declares OIO, OIO::Method, and OIO::Args via Exception::Class; Fields methods are generated at runtime from each class's fields definition. A direct class-method check confirms those methods are present, while the JVM execution of the real test fails in the exception path. This points to JVM runtime method lookup/invocation for dynamically installed methods in this path. Please trace the exact call site and preserve a focused regression test for both backends.
The archived run also reports shared-class failures (normalizedClass is null), object ID/reuse differences, and an unavailable Want::want_lvalue. These are recorded as additional failing symptoms, not yet attributed to the same cause. Want and Math::Random::MT::Auto are optional recommendations and were not installed for the target CPAN run.
Acceptance
Object::InsideOut4.05t/01-basic.tpasses on both JVM and interpreter backends.- Add project-owned regression coverage for dynamically generated exception subclass methods called through the exception construction/formatting path; validate it with system Perl first.
- Investigate and classify the other failing test programs, then verify the distribution suite with the relevant optional prerequisites installed.
- 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