Vote #66725
完了Crash while deleting in-use enumeration
0%
説明
So far, the problem only happens when running with "RAILS_ENV=development".
I get the following stack while deleting a priority still assigned to at least one issue:
TypeError (can't dump anonymous class Class):
/opt/ruby-enterprise-1.8.7/lib/ruby/1.8/yaml/rubytypes.rb:6:in to_yaml'quote'
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/quoting.rb:31:in
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb:236:in quote'quote_bound_value'
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:2392:in
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:2352:in replace_bind_variables'gsub'
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:2352:in
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:2352:in replace_bind_variables'sanitize_sql_array'
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:2341:in
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:2230:in sanitize_sql'merge_conditions'
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:1494:in
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:1492:in each'merge_conditions'
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:1492:in
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:1804:in add_conditions!'construct_finder_sql'
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:1687:in
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:1548:in find_every'find'
/opt/redmine-0.9.3/vendor/rails/activerecord/lib/active_record/base.rb:615:in
/opt/redmine-0.9.3/app/controllers/enumerations_controller.rb:84:in `destroy'
journals
Fixed in r3524.
It was raised when running test/functional/enumerations_controller.rb but not when running all functional tests with rake test:functionals. Very strange... Anyway, the code was firing a deprecation warning, so it has to be fixed.
Thanks for pointing it out.
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
SPAM
--------------------------------------------------------------------------------