Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

jshumate's latest activity

Friday, August 15 2008
785 Caching models fails in development was updated in Ruby on Rails
  • jshumate
    jshumate commented at 1:46 AM

    @Rob Anderton Original Ticket -- The new Rails.cache.fetch functionality in Rails 2.1 fails when caching ActiveRecord models on the second request in developmen...

Thursday, August 14 2008
785 Caching models fails in development was updated in Ruby on Rails
  • jshumate
    jshumate commented at 5:59 PM

    Looking at the patch from Tom Lea it would probably fix the stack level to deep issue when id goes missing, but it would not address the method missing issue fo...

  • jshumate
    jshumate commented at 4:34 PM

    I'm not sure exactly how to answer that. I am using edge with only a handful of plugins, all of them were disabled in my early tests to see where these seeming...

  • jshumate
    jshumate commented at 8:26 AM

    I think there are several deep questions regarding caching, but I thought they had moved to their own thread. This thread started with a report of behavior tha...

  • jshumate
    jshumate commented at 1:31 AM

    I have tested the attached patch and still have problems with methods disappearing from models on the second request. Running in production mode works fine. S...

Saturday, August 09 2008
774 Stack Error in method missing was updated in Ruby on Rails
  • jshumate
    jshumate commented at 4:52 PM

    With further digging this appears to be a symptom of the caching of objects on the second load during development that has been reported elsewhere.

Thursday, August 07 2008
774 Stack Error in method missing was updated in Ruby on Rails
  • jshumate
    jshumate commented at 6:32 PM

    I replaced the call to id on line 245 with readattribute('id') and have not been able to get it to fail since. Not sure why id would become undefined during op...

  • jshumate
    jshumate created the ticket at 4:55 PM

    I began having a problem with stack level too deep errors at different locations in my application after moving to rails 2.1. The code always seems to work aft...