PerlIO::via FILENO callback is omitted on open

Aberta
#2,162 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java, perl
Domínio
compilers

Direção de pesquisa

Start where a :via handle is opened and layers are pushed: inspect ViaLayer and LayeredIOHandle.fileno() to find the open/layer-setup path, then compare it with the callback-order probe in the issue. Run the gzip reproducer and t/001_roundtrip.t to confirm current behavior. Done means FILENO runs during open before the first WRITE with the expected layer and handle arguments, plus regression tests for ordering and initialization passing on JVM and interpreter backends.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

area:io bug

Summary

PerlOnJava does not invoke a PerlIO::via layer's FILENO callback when opening a :via(...) handle. Perl invokes this callback before the first WRITE. A layer that initializes its underlying stream in FILENO therefore reaches WRITE with no initialized state.

This breaks PerlIO-via-gzip 0.03 on both PerlOnJava execution backends. Its FILENO callback initializes IO::Compress::Gzip or IO::Uncompress::Gunzip, and its write/read callbacks require that initialization.

Reproducer

With PerlIO-via-gzip 0.03 available in @INC:

use PerlIO::via::gzip;
my $path = "/tmp/perlio-via-gzip-$$.gz";
open(my $fh, ">:via(gzip)", $path) or die "open: $!";
print {$fh} "hello\n";
close $fh or die "close: $!";
unlink $path;

System Perl completes this successfully. PerlOnJava emits an uninitialized-value warning from PerlIO::via::gzip::FLUSH, then dies from PerlIO::via::gzip::WRITE with handle not initialized.

A callback-order probe gives the minimal behavior difference. For a layer implementing PUSHED, FILENO, WRITE, and FLUSH, system Perl calls:

PUSHED,FILENO,WRITE,FLUSH

PerlOnJava calls:

PUSHED,WRITE,FLUSH,FLUSH,FLUSH

The FILENO callback is omitted on both JVM and interpreter backends.

CPAN and verification evidence

  • Distribution: PerlIO-via-gzip 0.03; upstream test: t/001_roundtrip.t.
  • PerlOnJava CPAN run: 20261120-195805-13340; the test exits after 5 of 10 planned tests with the uninitialized FLUSH warning and WRITE error described above.
  • At PerlOnJava source commit 506371c134837d026687b1958c856edb3c6f70e4, t/001_roundtrip.t passes all 10 tests on system Perl 5.34.1 and fails after test 5 with the same error on both the JVM and interpreter backends.
  • The repository nice -n 19 make gate passed at that commit.
  • The distribution is pure Perl; its runtime prerequisites are IO::Compress::Gzip and IO::Uncompress::Gunzip.

Environment and implementation notes

Reproduced on macOS 26.7.3 arm64 with OpenJDK 24.0.2.

ViaLayer discovers and implements onFileno(), and LayeredIOHandle.fileno() forwards to it when called. The observed difference is that opening a :via handle does not cause this callback to run before writes, as system Perl does. Please check where FILENO must be triggered during open/layer setup and preserve the callback's return/error semantics.

Acceptance criteria

  • A :via layer's FILENO callback runs during open, before its first read or write callback, matching system Perl.
  • The callback receives the same layer object and underlying handle arguments expected by PerlIO::via.
  • Add focused regression coverage for callback ordering and for a layer that depends on FILENO initialization.
  • t/001_roundtrip.t passes on system Perl, the PerlOnJava JVM backend, and the interpreter backend.
Linguagem predominante
Perl
Estrelas
67
Forks
8
Merge médio
4h 36min
PRs com merge (30d)
123

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de fglock/PerlOnJava

Todas as issues de fglock/PerlOnJava

Issues semelhantes

Mais issues de Perl

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.