Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Preserve state variables across file-reading loops

Aperta
  • Qualcosa non va?
#1,475 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
55/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java, perl
Ambito
compilers

Direzione di ricerca

Start with t/03-Nulls.t and t/04-Fix-Overlay.t, then trace the state-variable handling for source-file reads in both the JVM and interpreter backends. Preserve the filehandle loop, $. == 1 branch, and object assignment in a regression test. Done means both focused tests pass on both backends and the complete suite remains successful.

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

Descrizione

area:backend area:cpan-port area:runtime bug

Summary

DataExtract::FixedWidth 0.09 fails two upstream tests under PerlOnJava because a state variable declared inside a file-reading loop does not retain the constructed object between iterations. The first iteration should initialize $fw; on the next iteration $fw is undefined and the test dies calling parse.

Reproduction

This was found in CPAN random run 20260921-124328-13959 at PerlOnJava commit d8e4fd417.

The affected upstream tests are:

  • t/03-Nulls.t
  • t/04-Fix-Overlay.t

Both tests have the same relevant structure:

while (my $line = <$fh>) {
    state $fw;

    if ($. == 1) {
        $fw = DataExtract::FixedWidth->new({
            header_row   => $line,
            null_as_undef => 1, # or fix_overlay => 1
        });
    }
    else {
        my $arr_ref = $fw->parse($line);
    }
}

Under PerlOnJava, the constructor branch runs for the first line, but $fw is undefined on the second line. The test then dies with:

Can't call method "parse" on an undefined value

The failure reproduces when running the actual test files with both the JVM backend and the interpreter backend. It is not a timeout or a dependency-installation failure.

Expected behavior

state $fw should retain its value for subsequent loop iterations, as it does under standard Perl. The first line should construct a DataExtract::FixedWidth object and later lines should call parse on that same object.

Results

Standard Perl passes the focused tests:

t/03-Nulls.t ........ ok
t/04-Fix-Overlay.t .. ok
All tests successful.
Files=2, Tests=15

The archived standard-Perl oracle also passes the complete distribution suite: 18 test files, 82 tests.

PerlOnJava fails:

t/03-Nulls.t       exited 255; planned 12 tests, ran 0
t/04-Fix-Overlay.t exited 255; planned 3 tests, ran 0
Files=18, Tests=68
Failed 2/18 test programs

The remaining 16 test programs pass. The test files are reproducible on both PerlOnJava execution backends.

Suspected area

The immediate failure surface is lowering or runtime handling of file-scoped state variables in this loop context. The interaction with Perl's $. input-line counter is also worth checking: the initialization branch is selected using $. == 1, and PerlOnJava may be handling the line counter or its association with the newly opened filehandle differently in the failing source-file context.

A simple scalar state loop can appear to work in a minimal -e invocation, so the regression test should preserve the source-file form, filehandle read loop, $. == 1 branch, and object assignment shown above.

Environment and scope

  • Distribution: DataExtract::FixedWidth 0.09
  • PerlOnJava backends: JVM and interpreter
  • Standard Perl oracle: Perl 5.42.2 on macOS
  • Native/XS code: none
  • Reverse-dependency analysis: not applicable; this is a pure-Perl distribution

This is an upstream compatibility failure, not a failure caused by missing services, display requirements, native libraries, or unsupported XS code.

Lingua principale
Perl
Stelle
64
Fork
6
Merge medio
4h 29m
PR unite (30g)
185

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.