Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Dist::Zilla::Plugin::TrialVersionComment fails and times out

Abierto
#1,508 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
perl
Área
tooling

Línea de trabajo

The issue is in Dist::Zilla::Plugin::TrialVersionComment's integration with PPI under PerlOnJava. Start by examining the plugin's source, particularly the transformation of version assignments. Reproduce the failure using the CPAN test run details. Focus on object lifecycle and refcount issues noted in the repository's PPI support documentation. Create a minimal test case that isolates the problem without modifying upstream tests.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:backend area:cpan-port bug

Summary

Dist::Zilla::Plugin::TrialVersionComment-0.007 fails under PerlOnJava in
the CPAN compatibility run.

Evidence

  • CPAN run: 20260924-085657-82687

  • Failing test: t/01-basic.t

  • System Perl oracle: all 15 test files passed, 30 tests total.

  • PerlOnJava: the test command exceeded the 300-second runtime limit.

  • Before the timeout, the plugin produced:

    our $VERSION = '; # TRIAL
    

    The expected output preserves the version literal:

    our $VERSION = '0.001'; # TRIAL
    

The minimal standalone PPI parse/mutate/serialize operation reproduces the
expected output under PerlOnJava, so this appears to require the
Dist::Zilla/PPI integration path rather than being a generic PPI round-trip
failure.

Investigation notes

The repository's PPI support notes already identify unresolved PerlOnJava
object-lifecycle/refcount/DESTROY problems that may explain both the
corrupted transformed content and the long-running test process. This issue
should be reduced to a project-owned minimal reproducer before implementing a
fix; do not change the upstream test.

Acceptance criteria

  • Identify the root cause in the Dist::Zilla/PPI integration or PerlOnJava
    runtime.
  • Add a permanent focused regression test that passes under system Perl and
    both PerlOnJava backends where applicable.
  • Make the plugin's version assignment transformation preserve the original
    version literal and complete within normal test time.
  • Re-run the full Dist::Zilla::Plugin::TrialVersionComment test suite.
Lenguaje dominante
Perl
Estrellas
64
Forks
6
Merge medio
5 h 38 min
PR fusionados (30 d)
170

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fglock/PerlOnJava

Todos los issues de fglock/PerlOnJava

Issues similares

Más issues de Perl

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.