Note that there are some explanatory texts on larger screens.

plurals
  1. PORails 3.2.3: precompiling assets is failing with "No such file or directory - assets:precompile:all (Errno::ENOENT)"
    text
    copied!<p>I am using rails 3.2.3 and when i run bundle exec rake assets:precompile, it fails with following trace:</p> <pre><code>bundle exec rake assets:precompile --trace ** Invoke assets:precompile (first_time) ** Execute assets:precompile /home/harish/.rvm/rubies/ruby-1.8.7-p352/bin/ruby /home/harish/.rvm/gems/ruby-1.8.7-p352/bin/bundler_wrapper assets:precompile:all RAILS_ENV=production RAILS_GROUPS=assets --trace /home/harish/.rvm/gems/ruby-1.8.7-p352/bin/bundler_wrapper:22:in `read': No such file or directory - assets:precompile:all (Errno::ENOENT) from /home/harish/.rvm/gems/ruby-1.8.7-p352/bin/bundler_wrapper:22 rake aborted! Command failed with status (1): [/home/harish/.rvm/rubies/ruby-1.8.7-p352/b...] /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/file_utils.rb:53:in `create_shell_runner' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/file_utils.rb:45:in `call' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/file_utils.rb:45:in `sh' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/file_utils_ext.rb:39:in `sh' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/file_utils.rb:80:in `ruby' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/file_utils_ext.rb:39:in `ruby' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/actionpack-3.2.3/lib/sprockets/assets.rake:12:in `ruby_rake_task' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/actionpack-3.2.3/lib/sprockets/assets.rake:21:in `invoke_or_reboot_rake_task' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/actionpack-3.2.3/lib/sprockets/assets.rake:29 /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `call' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `execute' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `each' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/task.rb:158:in `invoke_with_call_chain' /home/harish/.rvm/rubies/ruby-1.8.7-p352/lib/ruby/1.8/monitor.rb:242:in `synchronize' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/task.rb:144:in `invoke' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/application.rb:116:in `invoke_task' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `top_level' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `each' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `top_level' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/application.rb:88:in `top_level' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/application.rb:66:in `run' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run' /home/harish/.rvm/gems/ruby-1.8.7-p352/gems/rake-0.9.2.2/bin/rake:33 /home/harish/.rvm/gems/ruby-1.8.7-p352/bin/rake:19:in `load' /home/harish/.rvm/gems/ruby-1.8.7-p352/bin/rake:19 /home/harish/.rvm/gems/ruby-1.8.7-p352/bin/bundler_wrapper:22 Tasks: TOP =&gt; assets:precompile </code></pre> <p>It is trying to look for the file "assets:precompile:all". When i create a dummy file with the name "assets:precompile:all", it runs successfully but without doing anything. Can somebody please help me to resolve this issue?</p>
 

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