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

Aperta
  • Qualcosa non va?
#2,023 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
perl
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Perl
Stelle
67
Fork
8
Merge medio
6h 14m
PR unite (30g)
143

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fglock/PerlOnJava

Tutte le issue di fglock/PerlOnJava

Issue simili

Altre issue su Perl

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.