Re: [RELEASE CANDIDATE] mod_perl-2.0.11 RC1
I'm seeing more test failures for 2.0.11 RC1 than for 2.0.10 with the same setup. Test Summary Report --- t/api/request_rec.t (Wstat: 0 Tests: 43 Failed: 0) Parse errors: Bad plan. You planned 55 tests but ran 43. t/compat/request.t(Wstat: 0 Tests: 12 Failed: 0) Parse errors: Bad plan. You planned 22 tests but ran 12. t/filter/in_bbs_inject_header.t (Wstat: 0 Tests: 36 Failed: 3) Failed tests: 22, 26, 30 Files=245, Tests=3392, 102 wallclock secs ( 0.76 usr 0.34 sys + 72.85 cusr 11.27 csys = 85.22 CPU) Result: FAIL Failed 3/245 test programs. 3/3392 subtests failed. The compat/request.t failures don't occur on the previous version. Is this expected? I'm using perl 5.28.0, and httpd 2.4.41 prefork. Adam On 9/2/19 8:34 AM, Steve Hay wrote: Please download, test, and report back on this mod_perl 2.0.11 release candidate. https://dist.apache.org/repos/dist/dev/perl/mod_perl-2.0.11-rc1.tar.gz MD5 = 417823274b32e5ca8759cf3760ad1591 SHA1 = e47c72337e6766c403d0a76b59d3808625e5162b Major changes in this release are as follows: Fix use-after-free segfault in ap_server_config_defines seen on start-up on OpenBSD. [Found/fixed by Sam Vaughan/Joe Orton] Fix build with Perls earlier than 5.13.6. [Rainer Jung ] Fix filter/in_bbs_inject_header.t test failure with Apache 2.4.25+. [Stefan Fritsch ] Fix apache/read.t test failure with Apache 2.4.25+. [Niko Tyni ]
Re: AW: STDOUT Problem migrating a site to mod_perl
On 23/09/2019 14:31, Andreas Mock wrote: Hi Thomas, why not implementing the follwoing steps. 1) create tmp file. 2) convert to tmp file 3) if everything worked fine reading file, setting appropriate headers and print content and afterwards delete tmp file. 4) if something went wrong you can send an error page with appropriate headers and code. I would avoid messing around with STDOUT. Best regards Andreas Thanks, That seems to work well, it just seems a shame to need to create a temp file. Interestingly later in the script where under a different condition it pipes into gs and out through stdout through the command line, and it works fine. -Ursprüngliche Nachricht- Von: Thomas Kenyon Gesendet: Montag, 23. September 2019 14:52 An: modperl@perl.apache.org Betreff: STDOUT Problem migrating a site to mod_perl I have run into an odd problem when migrating a site to use mod_perl. The script in question, builds some postscript into a variable, then uses psconvert (from Postscript::Convert) to change that into a png and sends that back to the webserver. (headers are set up earlier in the script). This seems to work well with mod_cgi but doesn't work with mod_perl using either ModPerl::Registry or ModPerl::PerlRun. Annoyingly psconvert doesn't return the converted image, instead it dumps it to a file (or stdout). I have tried to re-implement this using GSAPI, but GSAPI doesn't seem to build on any of my machines. (all debian 9/10 based). use PostScript::Convert; psconvert(\$ps, '%stdout%' , format => 'png', resolution => '72', paper_size => '6.5x4'); I've searched through as much documentation as I can find, and tried various things, but none seem to work. TIA for any guidance.
AW: STDOUT Problem migrating a site to mod_perl
Hi Thomas, why not implementing the follwoing steps. 1) create tmp file. 2) convert to tmp file 3) if everything worked fine reading file, setting appropriate headers and print content and afterwards delete tmp file. 4) if something went wrong you can send an error page with appropriate headers and code. I would avoid messing around with STDOUT. Best regards Andreas > -Ursprüngliche Nachricht- > Von: Thomas Kenyon > Gesendet: Montag, 23. September 2019 14:52 > An: modperl@perl.apache.org > Betreff: STDOUT Problem migrating a site to mod_perl > > I have run into an odd problem when migrating a site to use mod_perl. > > The script in question, builds some postscript into a variable, then > uses psconvert (from Postscript::Convert) to change that into a png and > sends that back to the webserver. (headers are set up earlier in the > script). > > This seems to work well with mod_cgi but doesn't work with mod_perl > using either ModPerl::Registry or ModPerl::PerlRun. > > Annoyingly psconvert doesn't return the converted image, instead it > dumps it to a file (or stdout). > > I have tried to re-implement this using GSAPI, but GSAPI doesn't seem to > build on any of my machines. (all debian 9/10 based). > > use PostScript::Convert; > psconvert(\$ps, '%stdout%' , format => 'png', resolution => '72', > paper_size => '6.5x4'); > > I've searched through as much documentation as I can find, and tried > various things, but none seem to work. > > TIA for any guidance.
