Typo crashiness when Akismet causes IO errors

This could probably stand to be made more robust–or at least to
display a meaningful error page, rather than the infamous “Application
Error (Rails)”.

Processing FeedbackController#bulkops (for 66.25.135.6 at 2006-12-07
14:00:53) [POST]
Session ID: e3785ed373860e57e005e0fe85796662
Parameters: {“search”=>"", “commit”=>“Confirm Classification of
Checked Items”, “action”=>“bulkops”, “controller”=>“admin/feedback”,
“feedback_check”=>{“3408”=>“on”, “3409”=>“on”}, “page”=>""}

Errno::EIO (Input/output error):
/vendor/akismet/akismet.rb:123:in write' /vendor/akismet/akismet.rb:123:incallAkismet’
/vendor/akismet/akismet.rb:166:in submitHam' /app/models/feedback.rb:137:inreport_as_ham’
/usr/local/lib/ruby/1.8/timeout.rb:56:in timeout' /app/models/feedback.rb:137:inreport_as_ham’
/app/models/content_state/ham.rb:21:in before_save' /app/models/content.rb:115:instate_before_save’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/callbacks.rb:344:in
callback' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/callbacks.rb:341:incallback’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/callbacks.rb:252:in
create_or_update' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/base.rb:1392:insave_without_validation’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/validations.rb:736:in
save_without_transactions' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/transactions.rb:126:insave’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/connection_adapters/abstract/database_statements.rb:51:in
transaction' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/transactions.rb:91:intransaction’
/usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/transactions.rb:118:in
transaction' /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/transactions.rb:126:insave’
/app/models/feedback.rb:156:in confirm_classification!' /app/controllers/admin/feedback_controller.rb:72:inbulkops’
/app/controllers/admin/feedback_controller.rb:71:in bulkops' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:941:inperform_action_without_filters’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:368:in
perform_action_without_benchmark' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:inperform_action_without_rescue’
/usr/local/lib/ruby/1.8/benchmark.rb:293:in measure' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/benchmarking.rb:69:inperform_action_without_rescue’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/rescue.rb:82:in
perform_action' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/base.rb:408:inprocess_without_filters’
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/filters.rb:377:in
process_without_session_management_support' /usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session_management.rb:117:inprocess’
/usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/dispatcher.rb:38:in
dispatch' /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:150:inprocess_request’
/usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:54:in
process!' /usr/local/lib/ruby/gems/1.8/gems/fcgi-0.8.7/lib/fcgi.rb:612:ineach_cgi’
/usr/local/lib/ruby/gems/1.8/gems/fcgi-0.8.7/lib/fcgi.rb:609:in
each_cgi' /usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:53:inprocess!’
/usr/local/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/fcgi_handler.rb:23:in
`process!’
/home/meta/typo/public/dispatch.fcgi:24

mathew

mathew [email protected] writes:

This could probably stand to be made more robust–or at least to
display a meaningful error page, rather than the infamous “Application
Error (Rails)”.

Yeah. Spam checking has been causing me grief in all sorts of annoying
ways recently. Once I’ve got a complete rspec specification suite
ported I shall be taking a very close look at it.