Note that there are some explanatory texts on larger screens.

plurals
  1. PORails 3 - psych.rb - couldn't parse YAML
    primarykey
    data
    text
    <p>While integrating backgroundrb-rails3 I get the following error,</p> <pre><code>~/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:in `parse': couldn't parse YAML at line 8 column 22 (Psych::SyntaxError) from ~/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:148:in `parse_stream' from ~/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:119:in `parse' from ~/.rvm/rubies/ruby-1.9.2-p290/lib/ruby/1.9.1/psych.rb:106:in `load' from ~/.rvm/gems/ruby-1.9.2-p290/gems/backgroundrb-rails3-1.1.6/lib/backgroundrb/bdrb_config.rb:27:in `read_config' from ~/workspace/artbee/Trunk/script/load_worker_env.rb:25:in `&lt;top (required)&gt;' from ~/.rvm/gems/ruby-1.9.2-p290/gems/packet-0.1.15/bin/packet_worker_runner:25:in `require' from ~/.rvm/gems/ruby-1.9.2-p290/gems/packet-0.1.15/bin/packet_worker_runner:25:in `initialize' from ~/.rvm/gems/ruby-1.9.2-p290/gems/packet-0.1.15/bin/packet_worker_runner:47:in `new' from ~/.rvm/gems/ruby-1.9.2-p290/gems/packet-0.1.15/bin/packet_worker_runner:47:in `&lt;top (required)&gt;' from ~/.rvm/gems/ruby-1.9.2-p290/bin/packet_worker_runner:19:in `load' from ~/.rvm/gems/ruby-1.9.2-p290/bin/packet_worker_runner:19:in `&lt;main&gt;' </code></pre> <p>I found a <a href="https://stackoverflow.com/questions/4980877/rails-error-couldnt-parse-yaml">similar question</a> in stack overflow and the accepted answer works for me.</p> <p>I don't want to use Syck, how can i fix it with Psych? Is there any difference in yml format for both? As the backtrace is not pointing to any yaml file, how can i debug more?</p> <p>Any help is highly appreciated...</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload