I experienced the error again today, and this time I was careful to note, the user experience is that the server goes away. Poof, gone. There’s no 500 error or anything; it’s as if the server was never there. I restarted the Dancer process, clicked refresh on web browser, and continued normally. I retried the same sequence of user actions that led to the error, but could not replicate.
Given the intermittency, and that the error appears to surface on any route, I’m starting to wonder if this is some sort of race condition within the before hook of the app? We do some pretty fancy stuff with the before hook to implement a certain feature of the app; maybe I should post some of that code? In any event, thanks for the continuing discussion. At the risk of encouraging bad habits, Chad, thanks for choosing this issue to procrastinate 😊 From: Andrew Beverley Sent: Thursday, March 14, 2019 11:56 AM To: Perl Dancer users mailing list Subject: Re: [dancer-users] Dancer crashing On Thu, 14 Mar 2019 11:47:31 -0700 Chad Wallace wrote: > > I don't know how else you would get the following fatal error, unless > > something is actually dying with the message "Use of uninitialized > > value in subroutine entry" > > > > Use of uninitialized value in subroutine entry at > > > > /home/hermann/perl5/perlbrew/perls/perl-5.26.2/lib/site_perl/5.26.2/HTTP/Server/Simple.pm > > line 397. > > That one's not fatal, but the one after it is. It's a croak from > within Socket's XS code. Ah, I see what you mean. I didn't scroll down enough :) Andy _______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
_______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
