[CPAN] Object-InsideOut 4.05 fails on JVM with generated exception Fields method
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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.
- 主要言語
- Perl
- スター
- 67
- フォーク
- 8
- 平均マージ
- 5時間 12分
- マージ済み PR(30日)
- 131
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
fglock/PerlOnJava のほかの issue
-
area:cpan-port bug
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
fglock/PerlOnJava#2153 ·
メンテナーはふだん 1 日以内に返信
-
area:cpan-port area:parser bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
fglock/PerlOnJava#2137 ·
メンテナーはふだん 1 日以内に返信
-
area:backend area:cpan-port area:runtime bug
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
fglock/PerlOnJava#2071 ·
メンテナーはふだん 1 日以内に返信
-
area:runtime documentation enhancement
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
fglock/PerlOnJava#1579 ·
メンテナーはふだん 1 日以内に返信
-
area:cpan-port bug
難易度 3/5 1〜2日 初心者へのやさしさ 62/100
fglock/PerlOnJava#2157 ·
メンテナーはふだん 1 日以内に返信
fglock/PerlOnJava の issue をすべて見る
似ている issue
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksオープンteam-cli
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 93/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
inverse-inc/packetfence#9728 ·
メンテナーはふだん 1 日以内に返信
-
fix(char-create): show the real reason a character is refused対応中かも @baphomello が 1 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
メンテナーはふだん 1 日以内に返信