CPAN: ORLite-Migrate 1.07 fails when IPC::Run3 spools input via File::Temp
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start with t/03_trivial.t and reproduce the failure on both JVM and interpreter backends using the archived CPAN run details. Trace how File::Temp::tempfile handles temporary filenames and IO handles in PerlOnJava, then compare that behavior with system Perl. Done means the migration test completes successfully on both backends while the full ORLite-Migrate test suite still passes.
由索引模型根據 Issue 內容生成。
描述
Summary
The upstream ORLite-Migrate 1.07 test suite fails on PerlOnJava when a migration patch is launched through IPC::Run3. IPC::Run3 tries to spool scalar input through File::Temp::tempfile; PerlOnJava reports an undefined temporary filename, then fails to remove the resulting empty path. The migration subprocess exits with status 255 and ORLite::Migrate aborts.
This is reproducible on both the JVM and interpreter backends. The same unmodified distribution and complete test suite pass under system Perl, so this is a PerlOnJava compatibility failure rather than an upstream test or setup failure.
Evidence
- Distribution:
ORLite-Migrate1.07; target recorded asORLite::Migrate::Perl. - CPAN tester run:
20261109-091152-39587. - System Perl oracle: Perl 5.42.2; all 3 test files and 10 tests pass.
- PerlOnJava: 5.44.1;
t/01_compile.tandt/02_main.tpass, whilet/03_trivial.texits early after its first assertion (4 planned). The failing test reproduces on both JVM and interpreter backends. - Failure path:
ORLite::Migratepasses migration input toIPC::Run3::run3;IPC::Run3reaches_spool_data_to_childand callstempfile. PerlOnJava warns about an uninitialized$fnameinFile::Temp, reports that removing file''failed, and then reportsMigration patch migrate-1.pl failed, database in unknown state.
Expected behavior
IPC::Run3 should receive a usable temporary file handle for the scalar input, pass the database filename to the migration subprocess, and allow the migration to complete as it does under system Perl.
Related work
Related to #1649, which tracks Perl ownership and resource-lifetime semantics. This CPAN case exercises a temporary IO handle, but the specific File::Temp failure has not yet been proven to share #1649's root cause. Please use it as an acceptance case when assessing that work.
Investigation notes
The CPAN run installed and tested the target's declared Perl dependencies. The failure is in temporary input spooling before the migration script can complete; the evidence does not point to SQLite behavior. The archived run and stable test name are included above so this report does not depend on local log paths.
- 主要語言
- Perl
- 星號
- 67
- 分支
- 8
- 平均合併
- 6 小時 14 分鐘
- 30 天內合併 PR
- 143
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
fglock/PerlOnJava 的其他 Issue
-
area:io area:warnings bug
難度 1/5 1 小時以內 新手友好度 88/100
fglock/PerlOnJava#2024 ·
維護者通常 1 天內回覆
-
area:runtime documentation enhancement
難度 2/5 1-3 小時 新手友好度 72/100
fglock/PerlOnJava#1579 ·
維護者通常 1 天內回覆
-
area:parser bug
難度 4/5 3-5 天 新手友好度 56/100
fglock/PerlOnJava#2027 ·
維護者通常 1 天內回覆
-
area:runtime bug
難度 4/5 3-5 天 新手友好度 52/100
fglock/PerlOnJava#2022 ·
維護者通常 1 天內回覆
-
area:backend area:cpan-port area:parser area:runtime bug
難度 4/5 3-5 天 新手友好度 54/100
fglock/PerlOnJava#2021 ·
維護者通常 1 天內回覆
查看 fglock/PerlOnJava 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 94/100
VEuPathDB/ApiCommonModel#260 ·
維護者通常 1 天內回覆
-
radius: unknown MFA in a source action crashes the RADIUS request可能已有人在做 @jrouzierinverse 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 76/100
inverse-inc/packetfence#9665 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 75/100
ibmdb/perl_DBD-DB2#21 ·
-
難度 2/5 1-3 小時 新手友好度 88/100
-
`config --theme` can't find theme files when the `~/Documents/Themes` directory is a symbolic link未關閉
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆