Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Stacktrace::Configurable loses anonymous caller metadata on both backends

Aberta
  • Algo errado?
#1,548 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
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
perl
Domínio
compilers

Direção de pesquisa

Start by running the five failing upstream tests: t/003-percent_s.t, t/004-percent_f.t, t/100-l4p.t, t/101-l4p_charY.t, and t/102-l4p_recursion.t, on both PerlOnJava backends. Trace the shared caller-stack and frame-metadata path used by Stacktrace::Configurable and the Log::Log4perl stack-trace layouts. Done means a focused regression test preserves the standard-Perl expectations for anonymous names, arguments, package/source formatting, and deparse data on both backends.

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

Descrição

area:backend area:cpan-port bug

Summary

The CPAN distribution Stacktrace-Configurable-0.06 fails under PerlOnJava because PerlOnJava does not preserve the same caller metadata used by Stacktrace::Configurable and Log::Log4perl::Layout::PatternLayout::Stacktrace.

This was observed in CPAN random tester run 20260928-091741-26386 for Log::Log4perl::Layout::PatternLayout::Stacktrace.

Evidence

  • Standard Perl passes the complete upstream suite: 14 files, 84 tests.
  • PerlOnJava fails 14 subtests in 5 files:
    • t/003-percent_s.t
    • t/004-percent_f.t
    • t/100-l4p.t
    • t/101-l4p_charY.t
    • t/102-l4p_recursion.t
  • The failure reproduces on both the JVM backend and the interpreter backend.
  • The failure is deterministic and does not involve XS/native code, missing services, display requirements, or a timeout.

Observed mismatches

The expected stack frames include anonymous caller information and arguments, for example:

__ANON__ (Log::Log4perl::Logger=HASH(...), "msg")

PerlOnJava instead reports forms such as:

debug

or, on the interpreter backend:

debug (Log::Log4perl::Logger=HASH(...), "msg")

Additional failures show incorrect package/file-name formatting in %s and %f, and closure deparsing that returns the wrong body (1+1 instead of the expected 2). The recursion-protection assertion itself passes, so the defect is specifically in stack-frame identity/argument/source metadata rather than the whole logging path.

Scope

The affected behavior is used by both Stacktrace::Configurable and Log::Log4perl stack-trace layouts. Please investigate the shared caller-stack/frame metadata path, including anonymous-sub naming, argument capture, package/source-name normalization, and source/deparse information exposed to stack-trace formatters.

The original CPAN failure was recorded as 14 failed subtests in the run identified above. A focused project regression test should preserve the standard-Perl expectations from the five failing upstream tests and pass on both PerlOnJava backends.

Linguagem predominante
Perl
Estrelas
64
Forks
6
Merge médio
4h 55min
PRs com merge (30d)
169

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.