I found the solution, at least in my case. I have a class defined in test/mock/development that uses 'require' vs. 'require_dependency'. Changing to require_dependency fixed the problem, which I can understand. I was not (at least it seemed) seeing the same error in test env, where I was using the same mock class. However, my test env of course does not cache classes as in dev, so my assumption was faulty.
Note: I had already downgraded to Rails 2.2 before finding the real problem. The (likely) related error I was getting in 2.2 is " NoMethodError Exception: You have a nil object when you didn't expect it! You might have expected an instance of Array. The error occurred while evaluating nil.include? " Luke On Sep 15, 7:01 pm, Luke <[email protected]> wrote: > I'm having the same issue discussed > herehttp://groups.google.com/group/rubyonrails-core/msg/787b561d166abf53 > > As reported elsewhere, in 2.3.2, the "Can't dupNilClass" error pops > up on the second request to a page, after a server restart. It seems > esp. "buggy" considering that you can bypass the error consistently by > setting config.cache_classes = true in development.rb (as in prod & > test environments). > > Anybody found a solution for this? > > Luke --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
