Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

On 1 February 2011 02:00, Eric Berg wrote: > I used 5.80030 to generate my files..it's a pretty new app. > > Just removing MooseX::NonMoose from just my Schema.pm did the trick. > > How do we edit these generated classes (such as MyApp::Schema) considering > the MD5 checks? Is there a protocol f

Re: [Catalyst] Opinions on static::simple - with caching

On 31 January 2011 19:04, Tomas Doran wrote: > On 31 Jan 2011, at 07:17, Toby Corkindale wrote: > >> However, I suppose in situations where that matters, you shouldn't be >> serving files via Static::Simple.. >> And the regular Static::Simple still provides Last-Modified headers, >> which do allo

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

I used 5.80030 to generate my files..it's a pretty new app. Just removing MooseX::NonMoose from just my Schema.pm did the trick. How do we edit these generated classes (such as MyApp::Schema) considering the MD5 checks? Is there a protocol for making that kind of change? Eric On 1/31/11 4:

[Catalyst] PostgreSQL Conference East: 2011 CFP

Following on the smashing success of PostgreSQL Conference West, PostgreSQL Conference West, The PostgreSQL Conference for Developers, End Users and Decision Makers, is being held at the Hotel Pennsylvania, in New York City from March 22nd through 25th 2011. Please join us in continuing to make thi

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

Yes, I know - but what if Eric used 0.7002 to generate files, as I did? ;) 2011/1/31 Justin Hunter : > if your DBIC schema is using Moose/MooseX::NonMoose, remove 'use > MooseX::NonMoose' from your base schema class. > http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=dbsrgits/DBIx-Class-Schema-Load

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

if your DBIC schema is using Moose/MooseX::NonMoose, remove 'use MooseX::NonMoose' from your base schema class. http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=dbsrgits/DBIx-Class-Schema-Loader.git;a=commitdiff;h=49643e1dff62e16331c30f51953d548d94da1d30 addressed this and any release beyond 0.07003

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

Seems, I had same problem. If your db schema classe (GLR::Schema) use Moose and MooseX::NonMoose, try to convert your schema classes to use strict/warning/base. If your schema class what generated by DBIx::Class::Schema::Loader, then upgrade it to latest and re-generate your classes. 2011/1/31 Er

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

$ uname -a Linux gonzo 2.6.32.12 #1 SMP Wed Apr 28 19:25:11 UTC 2010 i686 GNU/Linux $ cat /etc/debian_version 5.0.8 We wound up using cpanm to manually install/upgrade Moose, MooseX::Role::WithOverloading, DBIx::Class, Catalyst::Plugin::ConfigLoader, Catalyst. $ perl -MCatalyst -e 'print $Catalyst

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

It's a Linux box: Linux moby 2.6.35-24-generic #42-Ubuntu SMP Thu Dec 2 01:41:57 UTC 2010 i686 GNU/Linux and I'm running the latest Catalyst. Eric On 1/31/2011 8:37 AM, Peter Edwards wrote: On 31 January 2011 13:22, will trillich > wrote: Don't know ab

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

On 31 January 2011 13:22, will trillich wrote: > Don't know about this specific problem, but we just ran into something > similar -- no upgrades, no changes, but Catalyst suddenly stopped loading > (DBIx::Class::Schema::connection(): No arguments to load_classes). Wound up > having to cpanm a bun

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

Ok, at least I'm (arguably) not crazy. Justin Hunter suggested a few specific upgrades, and I'm going through my cpan updates and have found also that there are quite a number of masked versions where there are two separate versions installed, and the older one is masking the newer one. I'll

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

Don't know about this specific problem, but we just ran into something similar -- no upgrades, no changes, but Catalyst suddenly stopped loading (DBIx::Class::Schema::connection(): No arguments to load_classes). Wound up having to cpanm a bunch of upgrades by hand before it started working again.

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

have you tried upgrading namespace::clean, namespace::autoclean, Package::Stash and Package::Stash::XS (if you have it)? Justin On Mon, Jan 31, 2011 at 7:34 AM, Eric Berg wrote: > I have reverted to previously-known working versions and am having the same > problem. > > Any help that anyone can

Re: [Catalyst] Suddenly Failing with Moose and MOP Errors

I have reverted to previously-known working versions and am having the same problem. Any help that anyone can provide would most certainly be appreciated. This sucks. It's kind of ridiculous too. Thanks. Eric On 1/30/2011 8:34 PM, Eric Berg wrote: All of a sudden my application stopped w

[Catalyst] [ANNOUNCE] Catalyst-Runtime 5.80031

Hi It gives me great pleasure to announce the latest maintenance release in the Catalyst 5.80 series. This release mainly fixes a warning produced by applications deployed as FastCGI which was introduced in Catalyst-Runtime 5.80030. Full changelog below as always. Cheers t0m 5.80031 201

Re: [Catalyst] progressive authentication via db & LDAP

On 28 Jan 2011, at 16:34, piccard wrote: So put that logic in your domain model (i.e. DB row class), where it belongs? sorry, I'm not sure what u mean (new to Catalyst and DBIx). I need progressive authentication. No, you don't. First it should check against the db and then against the

Re: [Catalyst] Opinions on static::simple - with caching

On 31 Jan 2011, at 07:17, Toby Corkindale wrote: However, I suppose in situations where that matters, you shouldn't be serving files via Static::Simple.. And the regular Static::Simple still provides Last-Modified headers, which do allow browsers to perform some caching. What do you think?