crash log: No such pseudo-hash field "high_priority" at .../Stats.pm line 47

[Brad Fitzpatrick]

On Mon, 7 May 2007, Ask Bjørn Hansen wrote:

> > Since you can reproduce this, could you add something like,
> >
> >    unless (exists $be->{client}->{high_priority}) {
> >        warn "Our weird \$be->{client} is a $be->{client}!\n";
> >    }
> >
> > Then see what it says in production?  I'm wondering if some wrong
> > type is
> > getting assigned to that?
>
> Nope - that was my first guess too...
>
> 2007-05-07 14:09:34.488004500 Our weird $be->{client} is a
> Perlbal::ClientProxy=ARRAY(0x118a550)!
> 2007-05-07 14:09:34.576972500 Our weird $be->{client} is a
> Perlbal::ClientProxy=ARRAY(0x111e440)!
> 2007-05-07 14:09:34.576972500 Our weird $be->{client} is a
> Perlbal::ClientProxy=ARRAY(0x1122b80)!
>
> The patch attached below - apologies for the useless inline patch
> before.
>

Maybe ClientProxy's sub new_from_base's use of bless, to down-bless the
ClientHTTPBase is the problem?  But we would've hit this a long time ago.

I don't get it.

What version of Perl in dev vs. production?  I know the trickery we do
with re-blessing and fields.pm in Perlbal doesn't work in Perl 5.9.x, and
I've been meaning to care one of these days... maybe this is related.

- Brad