ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

TemplateError (found unexpected end of stream) during search (Bug #1251)

Added by Vladislav Poluhin at 2013-03-15 02:37 am. Updated at 2013-03-15 04:20 pm.

Status:Open Start date:2013-03-15
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Remote issue URL: Affected version:2.10.0

Description

Full traceback:

Processing SearchController#index (for 46.166.89.9 at 2013-03-15 09:34:23) [GET]
  Parameters: {"q"=>"django 1.5", "controller"=>"search", "action"=>"index", "id"=>"project"}
Rendering template within layouts/base
Rendering search/index

ActionView::TemplateError ((<unknown>): found unexpected end of stream while scanning a quoted scalar at line 13 column 3) on line #33 of app/views/search/index.rhtml:
30: 
31:     <dl id="search-results">
32:       <% @results.each do |e| %>
33:         <dt class="<%= e.event_type %>">
34:           <%= content_tag('span', h(e.project), :class => 'project') unless @project == e.project %>
35:           <%= link_to highlight_tokens(truncate(h(e.event_title), :length => 255), @tokens), e.event_url %>
36:         </dt>

    .rvm/rubies/ruby-1.9.3-p385/lib/ruby/1.9.1/psych.rb:203:in `parse'
    .rvm/rubies/ruby-1.9.3-p385/lib/ruby/1.9.1/psych.rb:203:in `parse_stream'
    .rvm/rubies/ruby-1.9.3-p385/lib/ruby/1.9.1/psych.rb:151:in `parse'
    .rvm/rubies/ruby-1.9.3-p385/lib/ruby/1.9.1/psych.rb:127:in `load'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/base.rb:3190:in `object_from_yaml'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/attribute_methods.rb:309:in `unserialize_attribute'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/attribute_methods.rb:286:in `read_attribute'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/base.rb:2801:in `block in attributes'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/base.rb:2801:in `each'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/base.rb:2801:in `attributes'
    app/models/journal.rb:83:in `details'
    app/models/issue.rb:41:in `block in <class:Issue>'
    app/views/search/index.rhtml:33:in `block in _run_rhtml_app47views47search47index46rhtml'
    app/views/search/index.rhtml:32:in `each'
    app/views/search/index.rhtml:32:in `_run_rhtml_app47views47search47index46rhtml'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_view/renderable.rb:34:in `block in render'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_view/base.rb:306:in `with_template'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_view/renderable.rb:30:in `render'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_view/template.rb:205:in `render_template'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_view/base.rb:265:in `render'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_view/base.rb:348:in `_render_with_layout'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_view/base.rb:262:in `render'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/base.rb:1252:in `render_for_file'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/base.rb:936:in `render'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/benchmarking.rb:51:in `block in render_with_benchmark'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/benchmarking.rb:51:in `render_with_benchmark'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/base.rb:1328:in `default_render'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/base.rb:1334:in `perform_action'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/filters.rb:617:in `call_filters'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/filters.rb:610:in `perform_action_with_filters'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/benchmarking.rb:68:in `block in perform_action_with_benchmark'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/benchmarking.rb:68:in `perform_action_with_benchmark'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/rescue.rb:160:in `perform_action_with_rescue'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/flash.rb:151:in `perform_action_with_flash'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/base.rb:532:in `process'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/filters.rb:606:in `process_with_filters'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/base.rb:391:in `process'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/base.rb:386:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/routing/route_set.rb:438:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/dispatcher.rb:87:in `dispatch'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/dispatcher.rb:121:in `_call'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/dispatcher.rb:130:in `block in build_middleware_stack'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/query_cache.rb:29:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/query_cache.rb:29:in `block in call'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/query_cache.rb:9:in `cache'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/query_cache.rb:28:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/activerecord-2.3.17/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/string_coercion.rb:25:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/params_parser.rb:15:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/session/cookie_store.rb:99:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/failsafe.rb:26:in `call'
    <internal:prelude>:10:in `synchronize'
    .rvm/gems/ruby-1.9.3-p385/gems/actionpack-2.3.17/lib/action_controller/dispatcher.rb:106:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/rails-2.3.17/lib/rails/rack/static.rb:31:in `call'
    .rvm/gems/ruby-1.9.3-p385/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:552:in `process_client'
    .rvm/gems/ruby-1.9.3-p385/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:632:in `worker_loop'
    .rvm/gems/ruby-1.9.3-p385/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:500:in `spawn_missing_workers'
    .rvm/gems/ruby-1.9.3-p385/gems/unicorn-4.6.2/lib/unicorn/http_server.rb:142:in `start'
    .rvm/gems/ruby-1.9.3-p385/gems/unicorn-4.6.2/bin/unicorn_rails:209:in `<top (required)>'
    /var/www//chiliproject/.rvm/gems/ruby-1.9.3-p385/bin/unicorn_rails:23:in `load'
    /var/www//chiliproject/.rvm/gems/ruby-1.9.3-p385/bin/unicorn_rails:23:in `<main>'

Rendering /var/www/chiliproject/public/500.html (500 Internal Server Error)

History

#1
Updated by Holger Just at 2013-03-15 03:31 pm

It looks like you used your ChiliProject database previously on Ruby 1.8 and moved to 1.9 now. Ruby 1.9 brings a new YAML engine (Psych instead of Syck). As Syck unfortunately sometimes produced YAML which is technically against the standard and subsequently isn't parseable by Psych, you get the error during parsing of journal changes (which are saved in YAML in the database).

As a temporary workaround, you could try to force Syck as a YAML engine which will probably remove the immediate error. You can do this by creating a new file in config/initializers/force_syck.rb containing this code:

require 'yaml'
YAML::ENGINE.yamler = 'syck'

In the long term, we will have to come up with a technique to transform the "old" yaml to be compliant and parsable by Psych. Probably something along the lines of http://darwinweb.net/articles/convert-syck-to-psych-yaml-format in a migration...

#2
Updated by Eric Wu at 2013-03-15 04:20 pm

Vladislav Poluhin wrote:

Full traceback:

[...]

....

Also available in: Atom PDF