On 19 Aug 2010, at 23:20, w...@serensoft.com wrote:
I'm not sure. This isn't just $c->something, It'd involve running
"catalyst.pl" to create a fresh MyApp with a two-character (or one-
character) name, which would then require some post-processing
cleanup.
I really don't think so.
You j
I'm not sure. This isn't just $c->something, It'd involve running "
catalyst.pl" to create a fresh MyApp with a two-character (or one-character)
name, which would then require some post-processing cleanup.
Is there a style guide for writing Catalyst tests?
On Thu, Aug 19, 2010 at 4:55 PM, Tomas
On 19 Aug 2010, at 22:17, w...@serensoft.com wrote:
How about
186:my ( $extension ) = ( $path =~ m{\.([^./]{1,4})$} );
instead?
Sure.
Could you write a failing test for this?
Cheers
t0m
___
List: Catalyst@lists.scsys.co.uk
Listinfo: htt
http://vig17261.kilretynud.com/
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.p
Hi,
I am just getting to learn Catalyst and have to admit that I am a bit lost. I
have so many questions that I will probably fire off more questions in the
near future.
Where am I today?
I have read THE BOOK, studied docs on CPAN, played around with DispatchTest
example from THE BOOK, but noth
Found a snag in Catalyst::Plugin::ConfigLoader (v0.27, also looks like it
applied to 0.28) on line 186:
186:my ( $extension ) = ( $path =~ m{\.(.{1,4})$} );
We created our app via "catalyst.pl QX", and all was well and good until we
started deploying versioned instances where the version
On 19 Aug 2010, at 19:32, Charlie Garrison wrote:
Good morning,
On 19/08/10 at 6:32 PM +0100, Ash Berlin
wrote:
if ( my $sid = $c->request->parameters->{$param} ) {
Try changing parameters to query_parameters. It sounds like hitting
params is causing it to read the body and mes
Good morning,
On 19/08/10 at 6:32 PM +0100, Ash Berlin
wrote:
if ( my $sid = $c->request->parameters->{$param} ) {
Try changing parameters to query_parameters. It sounds like
hitting params is causing it to read the body and mess things
up when it comes to read the body again.
W
On 19 Aug 2010, at 18:12, Charlie Garrison wrote:
> Good morning,
>
> On 19/08/10 at 9:12 AM -0700, Bryan Opfer wrote:
>
>> I have the same exact behavior in my app after upgrading to 0.14. So,
>> I don't think it is just your app. Interestingly, if I remove "param"
>> from my config and use t
Good morning,
On 19/08/10 at 9:12 AM -0700, Bryan Opfer wrote:
I have the same exact behavior in my app after upgrading to 0.14. So,
I don't think it is just your app. Interestingly, if I remove "param"
from my config and use the mode where the session id is appended to
the URI, then things
> I've tested with different clients and different servers; the behavior is
> consistent. I upgrade to C::P::Session::State::URI v0.14 and the problem
> starts. I downgrade to C::P::Session::State::URI v0.13 and the problem goes
> away.
>
> I failed to mention in my original message; the problem ma
Good morning,
On 19/08/10 at 1:17 PM +0100, Ash Berlin
wrote:
Caught exception in engine "Wrong Content-Length value: "
I see this error occasionally when I restart a server and the
client is in the middle of a request and retries. Does this
error happen every time? Including onc
On 19 Aug 2010, at 13:07, Charlie Garrison wrote:
> Good evening,
>
> I updated heaps of modules on my dev server last night, and my app broke
> horribly. Various errors in the log, common one being:
>
>Caught exception in engine "Wrong Content-Length value: "
I see this error occasion
Good evening,
I updated heaps of modules on my dev server last night, and my
app broke horribly. Various errors in the log, common one being:
Caught exception in engine "Wrong Content-Length value: "
I reverted to a backup and updated modules in small batches. The
error returned when
14 matches
Mail list logo
