[CPAN] Object-InsideOut 4.05 fails on JVM with generated exception Fields method

Offen
#2,038 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java, perl
Bereich
backend, devtools

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:backend area:cpan-port area:runtime bug

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 and Math::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.t with Can'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, and t/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::InsideOut 4.05 t/01-basic.t passes 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.
Vorherrschende Sprache
Perl
Sterne
67
Forks
8
Ø Merge
5 Std. 12 Min.
Gemergte PRs (30 T.)
131

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus fglock/PerlOnJava

Alle Issues in fglock/PerlOnJava

Ähnliche Issues

Weitere Issues zu Perl

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.