Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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

Open
#1,508 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
perl
Domain
tooling

Research direction

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.

Written by the indexing model from the issue text.

Description

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.
Dominant language
Perl
Stars
64
Forks
6
Avg merge
5h 38m
Merged PRs (30d)
170

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fglock/PerlOnJava

All issues in fglock/PerlOnJava

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.