Re: [Catalyst] Setting file handle as the response body generates warnings.

2013-11-20 Thread neil.lunn
On 21/11/2013 11:48 AM, Bill Moseley wrote: $ perl -MIO::Uncompress::Gunzip -le 'use Data::Dumper; print Dumper +IO::Uncompress::Gunzip->new( "Catalyst-Runtime-5.90051.tar.gz" )->getHeaderInfo' Actually with more reading on this getting the uncompressed size reliably can be a real pain, and

Re: [Catalyst] Setting file handle as the response body generates warnings.

2013-11-20 Thread neil.lunn
On 21/11/2013 1:04 PM, neil.lunn wrote: On 21/11/2013 11:48 AM, Bill Moseley wrote: $ perl -MIO::Uncompress::Gunzip -le 'use Data::Dumper; print Dumper +IO::Uncompress::Gunzip->new( "Catalyst-Runtime-5.90051.tar.gz" )->getHeaderInfo' Oh, and a test case outside of catalyst, noting the -s ope

Re: [Catalyst] Setting file handle as the response body generates warnings.

2013-11-20 Thread neil.lunn
On 21/11/2013 11:48 AM, Bill Moseley wrote: Seems noncompliance may be rampant. Anyway, sounds like Catalyst isn't quite supporting this kind of file handle as expected. John, is there anything you would want me to try? Hi Bill. Back to my original response, trying to get the size of thi

Re: [Catalyst] Setting file handle as the response body generates warnings.

2013-11-20 Thread Bill Moseley
On Wed, Nov 20, 2013 at 3:45 PM, neil.lunn wrote: > 2.3.1.2. Compliance > > > A compliant compressor must produce files with correct ID1, > ID2, CM, CRC32, and ISIZE, but may set all the other fields in > the fixed-length part of the header to default values (255 for

Re: [Catalyst] Setting file handle as the response body generates warnings.

2013-11-20 Thread neil.lunn
On 21/11/2013 4:08 AM, Bill Moseley wrote: On Wed, Nov 20, 2013 at 7:37 AM, Bill Moseley > wrote: On Wed, Nov 20, 2013 at 4:08 AM, neil.lunn mailto:n...@mylunn.id.au>> wrote: my $length = $body->getHeaderInfo Well, that's helpful. Thanks. Complet

Re: [Catalyst] Setting file handle as the response body generates warnings.

2013-11-20 Thread Bill Moseley
On Wed, Nov 20, 2013 at 7:37 AM, Bill Moseley wrote: > > On Wed, Nov 20, 2013 at 4:08 AM, neil.lunn wrote: > >> my $length = $body->getHeaderInfo > > > Well, that's helpful. Thanks. Completely missed that in the docs. > Well, except for the actual files I have no ISIZE: $VAR1 = {

Re: [Catalyst] Setting file handle as the response body generates warnings.

2013-11-20 Thread Bill Moseley
On Wed, Nov 20, 2013 at 4:08 AM, neil.lunn wrote: > my $length = $body->getHeaderInfo Well, that's helpful. Thanks. Completely missed that in the docs. -- Bill Moseley mose...@hank.org ___ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.

Re: [Catalyst] Setting file handle as the response body generates warnings.

2013-11-20 Thread neil.lunn
On 20/11/2013 3:01 PM, Bill Moseley wrote: I just updated: $ perl -MCatalyst -le 'print Catalyst->VERSION' 5.90051 I can debug more in the morning -- anything specific I should look at? I think the stat operators have this problem on any type of in memory filehandle. That is pretty easy to r