Happily coding away in a Rails 2.2.2 Bort based-app, when I suddenly
start getting this error after a few requests:
NoMethodError (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?):
/opt/local/lib/ruby/gems/1.8/gems/activerecord-2.2.2/lib/
active_record/attribute_methods.rb:142:in
`create_time_zone_conversion_attribute?'
/opt/local/lib/ruby/gems/1.8/gems/activerecord-2.2.2/lib/
active_record/attribute_methods.rb:75:in `define_attribute_methods'
This only appears if I authenticate to the application. I can make a
couple of requests, then i start getting the above error. While I
don't think I've made any changes to cause something like this, when
you're so far removed from the low-level bits of the framework, it's
hard to tell.
I've searched the net, and while I've found a few hits on this, there
are no solutions to be found.
This issue is apparently caused by not passing enough parameters to
the route helpers when you have nested resources. For example, I have
a gallery, which has a nested image resource. When generating links
in the view, I called the helper, but I didn't pass an array with both
the gallery and the image, only the image.
The first time presenting the view would work; the second, I would get
the stack trace, and from that point on the mongrel instance is
hooped, and would not serve any content. It would have to be
restarted.
I've fixed the view, and the problem is now resolved.
However, I'm concerned about being able to crash mongrel hard this
way.....
This issue is apparently caused by not passing enough parameters to
the route helpers when you have nested resources. For example, I have
a gallery, which has a nested image resource. When generating links
in the view, I called the helper, but I didn't pass an array with both
the gallery and the image, only the image.
The first time presenting the view would work; the second, I would get
the stack trace, and from that point on the mongrel instance is
hooped, and would not serve any content. It would have to be
restarted.
I've fixed the view, and the problem is now resolved.
However, I'm concerned about being able to crash mongrel hard this
way.....
I was getting similar errors I started using Rails.cache w/ Rails 2.2.2. I'm
using Webrick, not Mongrel. I gave up and went back to using my homegrown
caching. With you information about not enough parameters, I may go back and
try again.
Quoting KenM <Andawyr@gmail.com>:
>
> Some further information....
>
> This issue is apparently caused by not passing enough parameters to
> the route helpers when you have nested resources. For example, I have
> a gallery, which has a nested image resource. When generating links
> in the view, I called the helper, but I didn't pass an array with both
> the gallery and the image, only the image.
>
> The first time presenting the view would work; the second, I would get
> the stack trace, and from that point on the mongrel instance is
> hooped, and would not serve any content. It would have to be
> restarted.
>
> I've fixed the view, and the problem is now resolved.
>
> However, I'm concerned about being able to crash mongrel hard this
> way.....
>
I was getting similar errors I started using Rails.cache w/ Rails 2.2.2. I'm
using Webrick, not Mongrel. I gave up and went back to using my homegrown
caching. With you information about not enough parameters, I may go back and
try again.
I went back and looked hard at my code that was crashing. I was missing a
parameter to a yield statement. So Rails appears to be brittle around this
issue. And maybe Mongrel more brittle than Webrick.
Thanks for the hint. It is always nice to get rid of code that I have to
maintain in favor of builtin stuff that someone else maintains.
I've love to track down why this is happening in my case -- but no
time. Plus, that's the way thoughtbot does it in factory_girl, so
it's gotta be right
