This queue is for tickets about the Catalyst-View-Jemplate CPAN distribution.

Report information
The Basics
Id:
35609
Status:
open
Priority:
Low/Low

People
Owner:
Nobody in particular
Requestors:
ANDK [...] cpan.org
Cc:
AdminCc:

BugTracker
Severity:
Normal
Broken in:
0.06
Fixed in:
(no value)



Subject: Test broke on Jemplate 0.21
Since the upload of Jemplate-0.21 to CPAN I see the following test failure: # Failed test at t/01_live.t line 60. # Structures begin differing at: # $got->[0] = '' # $expected->[0] = 'text/javascript' # Looks like you failed 1 test of 18. Dubious, test returned 1 (wstat 256, 0x100) Failed 1/18 subtests Regards,
Subject: Test broke on Jemplate 0.21 - change in behavior of 'Jemplate::runtime_source_code'
From: itegebo@berkeley.edu
On Sat May 03 02:14:13 2008, ANDK wrote:
Show quoted text
> Since the upload of Jemplate-0.21 to CPAN I see the following test
failure:
Show quoted text
> > # Failed test at t/01_live.t line 60. > # Structures begin differing at: > # $got->[0] = '' > # $expected->[0] = 'text/javascript' > # Looks like you failed 1 test of 18. > Dubious, test returned 1 (wstat 256, 0x100) > Failed 1/18 subtests
It appears the API changed a bit and 'runtime_source_code()' now needs to be called with an argument, 'standard'. I've created bug #37813 to let them know Jemplate >0.21 has broken interface compatibility.
From: itegebo@berkeley.edu
On Sun Jul 20 16:09:03 2008, ITEGEBO wrote:
Show quoted text
> On Sat May 03 02:14:13 2008, ANDK wrote:
> > Since the upload of Jemplate-0.21 to CPAN I see the following test
> failure:
> > > > # Failed test at t/01_live.t line 60. > > # Structures begin differing at: > > # $got->[0] = '' > > # $expected->[0] = 'text/javascript' > > # Looks like you failed 1 test of 18. > > Dubious, test returned 1 (wstat 256, 0x100) > > Failed 1/18 subtests
> It appears the API changed a bit and 'runtime_source_code()' now needs > to be called with an argument, 'standard'. > > I've created bug #37813 to let them know Jemplate >0.21 has broken > interface compatibility.
I neglected to point out that 'runtime_source_code()' is mentioned as part of the Public API. In 0.20, it returned the runtime output while in >=0.21 it prints it. This leaves the '$output' variable containing '1': Catalyst::View::Jemplate::process # add runtime if ($data && $data->{runtime}) { $output = Jemplate->runtime_source_code(); use Data::Dumper; print STDERR Dumper( $output ); }
From: itegebo@berkeley.edu
On Sat Aug 16 15:19:10 2008, ITEGEBO wrote:
Show quoted text
> On Sun Jul 20 16:09:03 2008, ITEGEBO wrote:
> > On Sat May 03 02:14:13 2008, ANDK wrote:
> > > Since the upload of Jemplate-0.21 to CPAN I see the following test
> > failure:
> > > > > > # Failed test at t/01_live.t line 60. > > > # Structures begin differing at: > > > # $got->[0] = '' > > > # $expected->[0] = 'text/javascript' > > > # Looks like you failed 1 test of 18. > > > Dubious, test returned 1 (wstat 256, 0x100) > > > Failed 1/18 subtests
> > It appears the API changed a bit and 'runtime_source_code()' now needs > > to be called with an argument, 'standard'. > > > > I've created bug #37813 to let them know Jemplate >0.21 has broken > > interface compatibility.
> I neglected to point out that 'runtime_source_code()' is mentioned as > part of the Public API. In 0.20, it returned the runtime output while > in >=0.21 it prints it. This leaves the '$output' variable containing
'1':
Show quoted text
> > Catalyst::View::Jemplate::process > > # add runtime > if ($data && $data->{runtime}) { > $output = Jemplate->runtime_source_code(); > use Data::Dumper; > print STDERR Dumper( $output ); > } > >
Looks like the latest developer release of Jemplate resolves this issue (Jemplate-0.23_1).


This service runs on Request Tracker, is sponsored by The Perl Foundation, and maintained by Best Practical Solutions.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.