I just got this dumped to my console, presumably because I happened to
be logged in while a comment spammer was attempting to ply his trade:
#<ActiveRecord::Errors:0xb788b0e0 @errors={“blog_id”=>[“can’t be
blank”], “article_id”=>[“points to an item that is no longer available
for interaction”]}, @base=#<Comment:0xb788f014
@attributes={“allow_pings”=>nil, “name”=>nil, “permalink”=>nil,
“blog_name”=>nil, “updated_at”=>nil, “body_html”=>nil,
“blog”=>#<Blog:0xb7884024 @attributes={“id”=>“1”,
[…]
“use_gravatar”=>false, “limit_article_display”=>10,
“text_filter”=>“smartypants”}}>, “guid”=>nil, “body”=>“I use Firefox in
Ubuntu…”, “title”=>nil, “published”=>true,
“url”=>“http://zombiebase.50webs.org/”, “author”=>“Consumer Computer
Desktops Reviews”, “type”=>“Comment”, “text_filter_id”=>nil,
“excerpt”=>nil, “blog_id”=>nil, “trackbacks_count”=>nil,
“extended_html”=>nil, “ip”=>nil, “whiteboard”=>nil, “extended”=>nil,
“comments_count”=>nil, “article_id”=>1632, “user_id”=>nil,
“allow_comments”=>nil, “email”=>“[email protected]”, “created_at”=>nil,
“keywords”=>nil}, @user=nil, @new_record=true,
@errors=#<ActiveRecord::Errors:0xb788b0e0 …>, @observer_state=false,
[…]
What I’m wondering is, why did this go to stdout or stderr, and not to
the log?
I’ve been having my site wedge with a Rails application error from time
to time, I’m now wondering if it’s wedging because typo is attempting to
write to stdout/stderr?
mathew