[Catalyst-dev] Annoying undef warnings from CP::Static::Simple

Matt S Trout dbix-class at trout.me.uk
Sat May 31 08:00:37 GMT 2008


On Fri, May 30, 2008 at 06:35:11PM -0500, Dave Rolsky wrote:
> I'm getting a bunch of warnings from requests for static content that look 
> like this:
> 
>  Use of uninitialized value in length at
>  /usr/local/share/perl/5.8.8/Catalyst/Dispatcher.pm line 287.
> 
> The problem is that Catalyst::Dispatcher expects $c->req->match to be 
> defined, but it isn't when CPSS does the dispatching.
> 
> I'm not sure where this should be fixed. Should $c->req->match always be 
> set? Or should CD just not assume it is defined?

There's no $c->action at all when CPSS fires so I don't think I can really
see $c->req->match as making a lot of sense in that case.

This has already been reported via rt.cpan but sans test; if you can whip one
up there's no reason we can't add a defined() check.

-- 
      Matt S Trout       Need help with your Catalyst or DBIx::Class project?
   Technical Director                    http://www.shadowcat.co.uk/catalyst/
 Shadowcat Systems Ltd.  Want a managed development or deployment platform?
http://chainsawblues.vox.com/            http://www.shadowcat.co.uk/servers/



More information about the Catalyst-dev mailing list