Every time I've done something like that, Rails has pulled me up short with a "stack level too deep" error. That's usually the only way you can catch these things. Mistakes like this can't be caught automatically, since a partial calling itself can sometimes be valid (when displaying a tree, for instance).
--Matt Jones On Jun 11, 2:37 pm, Sam Kong <[email protected]> wrote: > Hi, > > When I called a page, the server choked like frozen. > I checked it with 'top' command and HDD(wa) was 95%. > There's no error or suspicious log. > > After wasting 2 hours, I found that a partial called it self. > In _a.html.erb > <%= render :partial => "a" %> > > Can rails detect such a mistake and stop proceeding and report it? > > Thanks. > > Sam > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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-talk?hl=en -~----------~----~----~----~------~----~------~--~---
