ViewGantt: ActionView::TemplateError (Bug #787)

Missed some lines:

Processing GanttsController#show (for 130.83.160.152 at 2011-12-21 15:58:48) [GET]
Parameters: {"project_id"=>"ti21uziv", "action"=>"show", "controller"=>"gantts"}
Rendering template within layouts/base
Rendering gantts/show

ActionView::TemplateError (comparison of Issue with Issue failed) on line #63 of app/views/gantts/show.html.erb:
60: # Width of the entire chart
61: g_width = (@gantt.date_to - @gantt.date_from + 1)*zoom
62:
63: @gantt.render(:top => headers_height + 8, :zoom => zoom, :g_width => g_width, :subject_width => subject_width)
64:
65: g_height = [(20 * (@gantt.number_of_rows + 6))+150, 206].max
66: t_height = g_height + headers_height

[...]

Found a similar problem under redmine: http://www.redmine.org/issues/7579

Holger Just wrote:

At first, sorry for the delay.

no problem at all :-)

Please report back on your results.

?> Issue.rebuild!
ActiveRecord::StaleObjectError: Attempted to update a stale object: Issue
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/locking/optimistic.rb:100:in `update_without_dirty'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/dirty.rb:146:in `update_without_timestamps'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/timestamp.rb:64:in `update_without_callbacks'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/callbacks.rb:282:in `update'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/base.rb:2927:in `create_or_update_without_callbacks'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/callbacks.rb:250:in `create_or_update'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/base.rb:2594:in `save_without_validation!'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/validations.rb:1099:in `save_without_dirty!'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/dirty.rb:87:in `save_without_transactions!'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/transactions.rb:200:in `save!'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/connection_adapters/abstract/database_statements.rb:136:in `transaction'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/transactions.rb:182:in `transaction'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/transactions.rb:200:in `save!'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/transactions.rb:208:in `rollback_active_record_state!'
    from /var/lib/gems/1.8/gems/activerecord-2.3.14/lib/active_record/transactions.rb:200:in `save!'
    from /var/www/chili-2.5.0/vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:187:in `rebuild!'
    from /var/www/chili-2.5.0/vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:184:in `call'
    from /var/www/chili-2.5.0/vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:184:in `rebuild!'
    from /var/www/chili-2.5.0/vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:184:in `each'
    from /var/www/chili-2.5.0/vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:184:in `rebuild!'
    from /var/www/chili-2.5.0/vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:194:in `call'
    from /var/www/chili-2.5.0/vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:194:in `rebuild!'
    from /var/www/chili-2.5.0/vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:191:in `each'
    from /var/www/chili-2.5.0/vendor/plugins/awesome_nested_set/lib/awesome_nested_set.rb:191:in `rebuild!'

Denny Schierz wrote:

?> Issue.rebuild!
ActiveRecord::StaleObjectError: Attempted to update a stale object: Issue

This happens if issues are updated by two processes (or users) at the same time. I guess you haven't stopped your ChiliProject and one of your users updated an issue at an unfortunate time. It should work if you stop your live ChiliProject before hand and make sure you are the only one accessing the database.

Holger Just wrote:

This happens if issues are updated by two processes (or users) at the same time. I guess you haven't stopped your ChiliProject and one of your users updated an issue at an unfortunate time. It should work if you stop your live ChiliProject before hand and make sure you are the only one accessing the database.

I've stopped Apache (no rake/chili processes are active), but results are the same.

hi,

any more ideas?

Other than "Issue.rebuild! should do the trick", no. You might be able to correct by hand by looking at the issues table and look for rows with empty lft or root_id fields. If none are missing, there might be issues with the same lft and root_id, which would be a data inconsistency too.

The only one I can see, is the first row:

lft root_id
1 1

all others are different (which I can see, with my less SQL Know How ;-) ..), but I think it's normal.

cu denny

My SQL:

mysql> select COUNT(), lft,root_id FROM issues GROUP BY lft,root_id HAVING COUNT()>1;
Empty set (0.00 sec)

mysql> select lft,root_id from issues where lft is null;
Empty set (0.00 sec)

mysql> select lft,root_id from issues where root_id is null;
Empty set (0.00 sec)

I'm not that firm in SQL either, but yeah, I meant issues where the pair root_id,lft is the same.

Could you attach here or send me from the issues table the following columns: id, lft, rgt, root_id, project_id, parent_id? Thanks!