CPAN: ORLite-Migrate 1.07 fails when IPC::Run3 spools input via File::Temp

オープン
#2,023 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
perl
領域
backend

調査の方向性

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 の本文から書いたものです。

説明

area:backend area:io area:runtime bug

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-Migrate 1.07; target recorded as ORLite::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.t and t/02_main.t pass, while t/03_trivial.t exits early after its first assertion (4 planned). The failing test reproduces on both JVM and interpreter backends.
  • Failure path: ORLite::Migrate passes migration input to IPC::Run3::run3; IPC::Run3 reaches _spool_data_to_child and calls tempfile. PerlOnJava warns about an uninitialized $fname in File::Temp, reports that removing file '' failed, and then reports Migration 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分
マージ済み PR(30日)
143

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

fglock/PerlOnJava のほかの issue

fglock/PerlOnJava の issue をすべて見る

似ている issue

Perl の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。