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

Ouverte
  • Quelque chose ne va pas ?
#2,023 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
perl
Domaine
backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Perl
Étoiles
67
Forks
8
Merge moyen
6 h 14 min
PR mergées (30 j)
143

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de fglock/PerlOnJava

Toutes les issues de fglock/PerlOnJava

Issues similaires

Plus d'issues Perl

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.