Very timely, as well; we had an out of memory condition this morning, which we did not have the tail end of the log for. Now that Iâ€™d added this, we will next time it happens.
Senior Software Engineer, Build/Release
Cross Country Automotive Services
One Cabot Road
Medford, MA 02155
p: (781) 306-3605
m: (978) 423-8977
e: [email protected]
From: Mark Beihoffer
Sent: Wednesday, October 20, 2010 1:06 AM
To: The elegant MVC web framework
Subject: Re: [Catalyst] Logging is not immediate
I tried that and it
On Mon, Oct 18, 2010 at 7:05 PM, Bill Moseley wrote:
On Mon, Oct 18, 2010 at 4:46 PM, Ken Beal wrote:
The issue is that when I call $c->log(), it doesnâ€™t output anything until the â€œURL callâ€� completes. This makes it difficult to watch a long-running process, because I donâ€™t see anything until itâ€™s done, and I donâ€™t know if itâ€™s hung up on something because I canâ€™t see the log output.
maybe try this: $c->log->_flush;
Or try: warn "I'm stuck in a loop and the web user is wondering why I'm taking so long and will likely hit reload any second now!\n";
List: [email protected]
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
Confidentiality Note: This e-mail message and any attachments may contain
confidential or privileged information. If you are not the intended recipient,
please notify me immediately by replying to this message and destroy all
copies of this message and any attachments. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...