I haven't experienced this Scott. I know the log format can be a bit confusing though. I sometimes put a bunch of returns before running an action so I can see everything associated with the action and have a big break before it. There's probably a method you could call to flush the logger at the end of the action.
Here's a quick snip for putting the *very* old non-buffered logger in. Probably only want this in dev, if at all (and this is not my recommended solution, just something you could try). http://ryandaigle.com/articles/2007/9/25/what-s-new-in-edge-rails-logging-gets-a-speed-bump Martin Emde Tw: @martinemde On Wed, Dec 2, 2009 at 9:13 PM, Scott Olmsted <[email protected]> wrote: > > I'm making enhancements to existing shopping cart code. When one clicks on > 'Checkout' on the cart page, the code deals with the stuff in the cart to > create the order, then redirects to a page to collect address information. > > Most of the time the log entries after the redirect are not written until > the next request comes in. I see only > > Redirected to http://localhost:3000/checkout > Completed in 150ms (DB: 17) | 302 Found [http://localhost/cart/update_totals > ] > > and not > > ...bunch of SQL... > Rendering template within layouts/site > Rendering checkout/addresses > Rendered checkout/_secure_blurb (0.6ms) > Rendered checkout/_footer (2.7ms) > Completed in 365ms (View: 262, DB: 17) | 200 OK [http://localhost/checkout > ] > > until the next request. > > Anyone encounter this? Anything can be done about it? > > Thanks much, > > Scott > > -- > SD Ruby mailing list > [email protected] > http://groups.google.com/group/sdruby -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
