| Newsgroups |
gmane.comp.web.mason.devel |
| Message-ID |
<[email protected]> |
Weekly todo activity, Jun 13 to Jun 20
New task #544: Add method to query the component root of a file-based component
Should be able to ask a component which of multiple
component roots it came from, if using multiple component
roots. Right now this is only available from the
{source_root_key} slot.
Mon Jun 14 Jonathan Swartz created task
http://www.masonhq.com/docs/todo/access.html?id=544
New task #545: Integrate David Wheeler's changes to the Apache testing code from stable into HEAD
David made the following changes:
* Add -d to point to the test directory as the server root
when starting Apache.
* Moved the log files into t/logs and the conf file(s) into
t/conf. Add these to cleanup list.
Tue Jun 15 Dave Rolsky created task
Dave Rolsky writes: Of course, this may all be done
differently once we move to Apache::Test
http://www.masonhq.com/docs/todo/access.html?id=545
New bug #546: Combination of <%shared> and subrequests can seg fault on Perl < 5.8.4
A component with a <%shared> section that is executed both
in the main request and in a subrequest may cause Perl to
seg fault. Exact conditions of the bug are difficult to pin
down; it is sometimes possible to tweak a seg faulting
component slightly to make it benign again.
This is a minimal component that reproduces the seg fault on
Perl 5.6.1:
<%shared>
my $foo;
</%shared>
<%init>
# ARGS
$foo = "hi";
unless ($m->is_subrequest) {
$m->subexec($m->current_comp->path);
$m->abort();
}
</%init>
Replacing the "# ARGS" comment with "my $bar" will eliminate
the seg fault on Perl 5.6.1, but still cause a seg fault on
Perl 5.8.3. (See
http://www.masonhq.com/docs/manual/Params.html#define_args_h
ash for why this comment is significant to Mason.)
The seg fault could not be reproduced on Perl 5.8.4, leading
us to believe that the bug was fixed in that version.
We have tried tweaking internal code to eliminate the
problem without success. In any event, with this kind of
bug, doing a random code tweak might eliminate the seg fault
in one component but cause a new seg fault in a different
component.
For 5.6.1 users, removing any mention of ARGS from the
component appears to eliminate the seg fault. For 5.8.3
users, we recommend an upgrade to 5.8.4.
Thu Jun 17 Jonathan Swartz created bug
Jonathan Swartz set version_found to 1.10
Jonathan Swartz set difficulty to 3
Jonathan Swartz set severity to Normal
Jonathan Swartz set version_goal to Never
http://www.masonhq.com/docs/todo/access.html?id=546
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND