Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't know how to build task 'assets:precompile:primary' #187

Closed
greyblake opened this issue Feb 8, 2014 · 35 comments
Closed

Don't know how to build task 'assets:precompile:primary' #187

greyblake opened this issue Feb 8, 2014 · 35 comments

Comments

@greyblake
Copy link

@greyblake greyblake commented Feb 8, 2014

Description

I added monologue to Gemfile, ran bundle install.

Now on attempt to run any of rake tasks I got this error:

 bundle exec rake monologue:install:migrations
rake aborted!
Don't know how to build task 'assets:precompile:primary'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/tinymce-rails-3.5.6/lib/tasks/tinymce-assets.rake:1:in `<top (required)>'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/activesupport-4.0.1/lib/active_support/dependencies.rb:223:in `load'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/activesupport-4.0.1/lib/active_support/dependencies.rb:223:in `block in load'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/activesupport-4.0.1/lib/active_support/dependencies.rb:214:in `load_dependency'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/activesupport-4.0.1/lib/active_support/dependencies.rb:223:in `load'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/railties-4.0.1/lib/rails/engine.rb:641:in `block in run_tasks_blocks'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/railties-4.0.1/lib/rails/engine.rb:641:in `each'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/railties-4.0.1/lib/rails/engine.rb:641:in `run_tasks_blocks'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/railties-4.0.1/lib/rails/application.rb:243:in `block in run_tasks_blocks'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/railties-4.0.1/lib/rails/engine/railties.rb:17:in `each'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/railties-4.0.1/lib/rails/engine/railties.rb:17:in `each'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/railties-4.0.1/lib/rails/application.rb:243:in `run_tasks_blocks'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/railties-4.0.1/lib/rails/engine.rb:446:in `load_tasks'
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/railties-4.0.1/lib/rails/railtie/configurable.rb:30:in `method_missing'
/home/blake/poligon/rails_blog_engine/theblog/Rakefile:6:in `<top (required)>'
(See full trace by running task with --trace)

Environment

  • ruby 2.0.0p353 (2013-11-22 revision 43784) [x86_64-linux]
  • Rails 4.0.1
@greyblake
Copy link
Author

@greyblake greyblake commented Feb 8, 2014

It turned out that was installed manologue version 0.2.0, because 0.3.0 has a strange dependecy which bundle can't resolve: sass-rails ~> 3.2.3.
However it works from master. Could you please release a new patch(or minor) version with correct sass-rails dependency?

@jipiboily
Copy link
Owner

@jipiboily jipiboily commented Feb 8, 2014

What version of Rails are you using? I suspect you are using Rails 4, for which there is no official version other than master right now. /cc @msevestre

@greyblake
Copy link
Author

@greyblake greyblake commented Feb 8, 2014

Yes, rails 4. Thanks.

@msevestre
Copy link
Collaborator

@msevestre msevestre commented Feb 8, 2014

@jibiboily We should probably release the 0.4.0 version of monologue
compatible with Rails4 don't you think?

On Sat, Feb 8, 2014 at 12:20 PM, Sergey Potapov notifications@github.comwrote:

Yes, rails 4. Thanks.


Reply to this email directly or view it on GitHubhttps://github.com//issues/187#issuecomment-34549610
.

@jipiboily
Copy link
Owner

@jipiboily jipiboily commented Feb 8, 2014

@msevestre sure.

I did not try Monologue with Rails 4 just yet, did you? Any flaws?

Can you take care of the new release?

@strickland84
Copy link

@strickland84 strickland84 commented Feb 8, 2014

+1 for this! Just encountered the same error when running 'bundle exec rake monologue:install:migrations' on rails 4.0.0

@asahu8
Copy link

@asahu8 asahu8 commented Feb 11, 2014

Yes, this issue exists when tried to install Gem in Rails 4.

@jmzbond
Copy link

@jmzbond jmzbond commented Feb 11, 2014

It also happened to me when I'm installing in Rails 4, though I also have Monologue 2.0 because of the Sass-Rails dependency constraint.

@rept
Copy link

@rept rept commented Mar 21, 2014

Same problem. Any news?

@greyblake
Copy link
Author

@greyblake greyblake commented Mar 21, 2014

Well. Probably it's not the best idea... But I've created my own blog engine https://github.com/greyblake/blogo . In most sense it's pretty similar to monologue. But currently it's a bit raw and the good doc is missing.

@msevestre
Copy link
Collaborator

@msevestre msevestre commented Mar 21, 2014

Too bad you're not trying to fix whatever issue you might have and submit a
PR
On Mar 21, 2014 1:25 PM, "Sergey Potapov" notifications@github.com wrote:

Well. Probably it's not the best idea... But I've created my own blog
engine https://github.com/greyblake/blogo . In most sense it's pretty
similar to monologue. But currently it's a bit raw and the good doc is
missing.


Reply to this email directly or view it on GitHubhttps://github.com//issues/187#issuecomment-38300699
.

@greyblake
Copy link
Author

@greyblake greyblake commented Mar 21, 2014

I was about to do it but there are some reasons why I've decided to do what I did:

  1. I dislike the fact that some migrations have iterations through models (it's kind of bad practice, but I know it can be fixed)
  2. I had wanted to have support for multiple markup formats by design.
@msevestre
Copy link
Collaborator

@msevestre msevestre commented Mar 21, 2014

I am curious. Why is accessing the model in a migration bad practice? Not
each migration deals with adding or removing a column in a database. I
would love your input on that. Thanks
On Mar 21, 2014 5:08 PM, "Sergey Potapov" notifications@github.com wrote:

I was about to do it but there some reasons why I've decided to do what I
did:

  1. I dislike the fact that some migrations have iterations through models
    (it's kind of bad practice, but I know it can be fixed)
  2. I had wanted to have support for multiple markup formats by design.


Reply to this email directly or view it on GitHubhttps://github.com//issues/187#issuecomment-38324418
.

@greyblake
Copy link
Author

@greyblake greyblake commented Mar 21, 2014

Ok, there are some reasons:

  • If you already have many records in DB (thounds or millions?)
    • You may run out of memory unless you iterate with find_in_batch
    • It will be really slow
  • It may cause a behaviour that will take hours to investigate: loading records in migration make AR establish a model. So if the next migations add/remove/rename columns AR will not be aware of it. And it can result into SQL error with invalid columns. In this case it's necessary at least to call Model.reset_column_information
@jipiboily
Copy link
Owner

@jipiboily jipiboily commented Mar 22, 2014

Using find_each would totally be a good idea and really easy to fix. It's using find_in_batches under the hood.

You can do Markdown with https://github.com/jipiboily/monologue-markdown.

That said, I can understand you prefer to start fresh, it's all up to you! :)

@jipiboily
Copy link
Owner

@jipiboily jipiboily commented Mar 22, 2014

Anyone still having this exact issue by the way?

@relaxed-tomato
Copy link

@relaxed-tomato relaxed-tomato commented Apr 2, 2014

Hey guys, just following the thread, and I am getting the exact issue when I run bundle exec rake monologue:install:migrations

Don't know how to build task 'assets:precompile:primary'

@relaxed-tomato
Copy link

@relaxed-tomato relaxed-tomato commented Apr 3, 2014

Actually - using some of the files on the git repo helped me get past this problem, however, implementing this seems quite daunting. I am going to try putting together a blog from scratch, it may end up taking the same amount of time, let's see. Do you have any recommendations for creating a blog from scratch, any links or sites? I want the basics, article/images/authenticatino.

@msevestre
Copy link
Collaborator

@msevestre msevestre commented Apr 3, 2014

Hey Richard,

What do you mean with your first sentence? Which files are you taking about on which implementation is required? I would love to understand the issue here to be able to fix it. Thanks

On Apr 2, 2014, at 8:32 PM, Richard notifications@github.com wrote:

Actually - using some of the files on the git repo helped me get past this problem, however, implementing this seems quite daunting. I am going to try putting together a blog from scratch, it may end up taking the same amount of time, let's see. Do you have any recommendations for creating a blog from scratch, any links or sites? I want the basics, article/images/authenticatino.


Reply to this email directly or view it on GitHub.

@Ronelyn
Copy link

@Ronelyn Ronelyn commented Apr 3, 2014

Richard, I'm having the issue. Something of a Rails novice, but a very experienced tester. I'll be happy to work directly with you guys to debug and track down the problem.

@relaxed-tomato
Copy link

@relaxed-tomato relaxed-tomato commented Apr 5, 2014

Sorry guys, I decided the do it from scratch approach. Thanks for your messages, however, I prefer not to revisit this as I am limited on time. Thanks again.

@dlupu
Copy link

@dlupu dlupu commented Apr 5, 2014

Also having this issue with a rails 4.1 app.
+1 for a release with Rails 4+ compatibility

@msevestre
Copy link
Collaborator

@msevestre msevestre commented Apr 6, 2014

looking at the stack trace given above
/home/blake/.rvm/gems/ruby-2.0.0-p353@bf_clients/gems/tinymce-rails-3.5.6/lib/tasks/tinymce-assets.rake:1:in <top (required)>'

It seems that tinymce is still referenced somewhere. This is peculiar are we are using ckeditor now.

@msevestre
Copy link
Collaborator

@msevestre msevestre commented Apr 6, 2014

Ok I want to release a new gem this week. I would appreciate any gemfile.lock, stacktrace etc.. that could help me understand where is the problem coming from. Thanks all for your help

@Ronelyn
Copy link

@Ronelyn Ronelyn commented Apr 7, 2014

msevestre, my stack trace looks pretty similar to the one at the top. Appending here:

rake monologue:install:migrations --trace
rake aborted!
Don't know how to build task 'assets:precompile:primary'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/task_manager.rb:62:in []' c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/task.rb:353:in[]'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/tinymce-rails-3.5.6/lib/tasks/tinymce-assets.rake:1:in <top (required)>' c:/Ruby200/lib/ruby/gems/2.0.0/gems/activesupport-4.0.3/lib/active_support/dependencies.rb:223:inload'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/activesupport-4.0.3/lib/active_support/dependencies.rb:223:in block in load' c:/Ruby200/lib/ruby/gems/2.0.0/gems/activesupport-4.0.3/lib/active_support/dependencies.rb:214:inload_dependency'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/activesupport-4.0.3/lib/active_support/dependencies.rb:223:in load' c:/Ruby200/lib/ruby/gems/2.0.0/gems/railties-4.0.3/lib/rails/engine.rb:641:inblock in run_tasks_blocks'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/railties-4.0.3/lib/rails/engine.rb:641:in each' c:/Ruby200/lib/ruby/gems/2.0.0/gems/railties-4.0.3/lib/rails/engine.rb:641:inrun_tasks_blocks'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/railties-4.0.3/lib/rails/application.rb:243:in block in run_tasks_blocks' c:/Ruby200/lib/ruby/gems/2.0.0/gems/railties-4.0.3/lib/rails/engine/railties.rb:17:ineach'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/railties-4.0.3/lib/rails/engine/railties.rb:17:in each' c:/Ruby200/lib/ruby/gems/2.0.0/gems/railties-4.0.3/lib/rails/application.rb:243:inrun_tasks_blocks'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/railties-4.0.3/lib/rails/engine.rb:446:in load_tasks' c:/Ruby200/lib/ruby/gems/2.0.0/gems/railties-4.0.3/lib/rails/railtie/configurable.rb:30:inmethod_missing'
C:/dev/#######/#######/Rakefile:6:in <top (required)>' c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/rake_module.rb:28:inload'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/rake_module.rb:28:in load_rakefile' c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/application.rb:677:inraw_load_rakefile'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/application.rb:94:in block in load_rakefile' c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/application.rb:176:instandard_exception_handling'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/application.rb:93:in load_rakefile' c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/application.rb:77:inblock in run'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/application.rb:176:in standard_exception_handling' c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/lib/rake/application.rb:75:inrun'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/rake-10.2.2/bin/rake:33:in <top (required)>' c:/Ruby200/bin/rake:23:inload'
c:/Ruby200/bin/rake:23:in `

'

@Ronelyn
Copy link

@Ronelyn Ronelyn commented Apr 7, 2014

Here's my gemfile.lock, if that helps:

GEM
remote: https://rubygems.org/
specs:
actionmailer (4.0.3)
actionpack (= 4.0.3)
mail (> 2.5.4)
actionpack (4.0.3)
activesupport (= 4.0.3)
builder (
> 3.1.0)
erubis (> 2.7.0)
rack (
> 1.5.2)
rack-test (> 0.6.2)
activemodel (4.0.3)
activesupport (= 4.0.3)
builder (
> 3.1.0)
activerecord (4.0.3)
activemodel (= 4.0.3)
activerecord-deprecated_finders (> 1.0.2)
activesupport (= 4.0.3)
arel (
> 4.0.0)
activerecord-deprecated_finders (1.0.3)
activesupport (4.0.3)
i18n (> 0.6, >= 0.6.4)
minitest (
> 4.2)
multi_json (> 1.3)
thread_safe (
> 0.1)
tzinfo (> 0.3.37)
arel (4.0.2)
atomic (1.1.14)
bcrypt-ruby (3.1.2)
bcrypt-ruby (3.1.2-x86-mingw32)
builder (3.1.4)
capybara (2.2.1)
mime-types (>= 1.16)
nokogiri (>= 1.3.3)
rack (>= 1.0.0)
rack-test (>= 0.5.4)
xpath (
> 2.0)
coffee-rails (4.0.1)
coffee-script (>= 2.2.0)
railties (>= 4.0.0, < 5.0)
coffee-script (2.2.0)
coffee-script-source
execjs
coffee-script-source (1.6.3)
cucumber (1.3.10)
builder (>= 2.1.2)
diff-lcs (>= 1.1.3)
gherkin (> 2.12)
multi_json (>= 1.7.5, < 2.0)
multi_test (>= 0.0.2)
cucumber-rails (1.4.0)
capybara (>= 1.1.2)
cucumber (>= 1.2.0)
nokogiri (>= 1.5.0)
rails (>= 3.0.0)
database_cleaner (1.2.0)
devise (3.2.2)
bcrypt-ruby (
> 3.0)
orm_adapter (> 0.1)
railties (>= 3.2.6, < 5)
thread_safe (
> 0.1)
warden (> 1.2.3)
diff-lcs (1.2.5)
erubis (2.7.0)
execjs (2.0.2)
factory_girl (4.4.0)
activesupport (>= 3.0.0)
factory_girl_rails (4.4.1)
factory_girl (
> 4.4.0)
railties (>= 3.0.0)
gherkin (2.12.2)
multi_json (> 1.3)
gherkin (2.12.2-x86-mingw32)
multi_json (
> 1.3)
hike (1.2.3)
i18n (0.6.9)
jbuilder (2.0.2)
activesupport (>= 3.0.0)
multi_json (>= 1.2.0)
jquery-rails (3.0.4)
railties (>= 3.0, < 5.0)
thor (>= 0.14, < 2.0)
json (1.8.1)
mail (2.5.4)
mime-types (> 1.16)
treetop (
> 1.4.8)
mime-types (1.25.1)
mini_portile (0.5.2)
minitest (4.7.5)
multi_json (1.8.4)
multi_test (0.0.3)
mysql2 (0.3.14)
nokogiri (1.6.1)
mini_portile (> 0.5.0)
nokogiri (1.6.1-x86-mingw32)
mini_portile (
> 0.5.0)
orm_adapter (0.5.0)
polyglot (0.3.4)
rack (1.5.2)
rack-test (0.6.2)
rack (>= 1.0)
rails (4.0.3)
actionmailer (= 4.0.3)
actionpack (= 4.0.3)
activerecord (= 4.0.3)
activesupport (= 4.0.3)
bundler (>= 1.3.0, < 2.0)
railties (= 4.0.3)
sprockets-rails (> 2.0.0)
railties (4.0.3)
actionpack (= 4.0.3)
activesupport (= 4.0.3)
rake (>= 0.8.7)
thor (>= 0.18.1, < 2.0)
rake (10.1.1)
rdoc (4.1.1)
json (
> 1.4)
rspec-expectations (2.14.4)
diff-lcs (>= 1.1.3, < 2.0)
sass (3.2.13)
sass-rails (4.0.1)
railties (>= 4.0.0, < 5.0)
sass (>= 3.1.10)
sprockets-rails (> 2.0.0)
sdoc (0.4.0)
json (
> 1.8)
rdoc (> 4.0, < 5.0)
sprockets (2.11.0)
hike (
> 1.2)
multi_json (> 1.0)
rack (
> 1.0)
tilt (> 1.1, != 1.3.0)
sprockets-rails (2.0.1)
actionpack (>= 3.0)
activesupport (>= 3.0)
sprockets (
> 2.8)
thor (0.18.1)
thread_safe (0.1.3)
atomic
tilt (1.4.1)
treetop (1.4.15)
polyglot
polyglot (>= 0.3.1)
turbolinks (2.2.0)
coffee-rails
tzinfo (0.3.38)
uglifier (2.4.0)
execjs (>= 0.3.0)
json (>= 1.8.0)
warden (1.2.3)
rack (>= 1.0)
xpath (2.0.0)
nokogiri (~> 1.3)

PLATFORMS
ruby
x86-mingw32

DEPENDENCIES
coffee-rails (> 4.0.0)
cucumber-rails (>= 1.4.0)
database_cleaner (>= 1.2.0)
devise
factory_girl_rails (
> 4.0)
jbuilder
jquery-rails
mysql2 (= 0.3.14)
rails (= 4.0.3)
rspec-expectations (>= 2.14.4)
sass-rails (~> 4.0.0)
sdoc
turbolinks
uglifier (>= 1.3.0)

@Ronelyn
Copy link

@Ronelyn Ronelyn commented Apr 7, 2014

I can also email you info if you'd like; happy to help y'all improve, but as I said I'm a Ruby n00b!e, so I may not know what's most helpful. :)

@msevestre
Copy link
Collaborator

@msevestre msevestre commented May 17, 2014

Thanks all for your feedback. I could push in production today a new app using the master version of monologue. This version is the only one compatible with rails 4.
If you are experiencing more issues please feel free to reopen it.
In the meantime I will release a new gem on Monday.

@msevestre msevestre closed this May 17, 2014
@msevestre
Copy link
Collaborator

@msevestre msevestre commented May 23, 2014

Hi all,
I have just released the 0.4.0 version of monologue compatible with rails 4. Enjoy

@djvs
Copy link

@djvs djvs commented Dec 8, 2014

msevestre: Problem still exists with default install of Rails 4 and Monologue. Special 0.4.0 gem available anywhere? Use github?

@msevestre
Copy link
Collaborator

@msevestre msevestre commented Dec 8, 2014

That's weird. I thought that was fixed. There is definitely a 0.4.1 gem
available https://rubygems.org/gems/monologue
Can you post your gemfile.lock? thanks

On Mon, Dec 8, 2014 at 5:44 PM, djvs notifications@github.com wrote:

msevestre: Problem still exists with default install of Rails 4 and
Monologue. Special 0.4.0 gem available anywhere?


Reply to this email directly or view it on GitHub
#187 (comment).

@djvs
Copy link

@djvs djvs commented Dec 8, 2014

Consider writing in README.md:

gem 'monologue', '<~ 0.4.0' # requires Rails 4.0.4 or greater

@rwbrown72
Copy link

@rwbrown72 rwbrown72 commented Dec 9, 2014

Just FYI... I was running into the same issue as above. I moved down to gem 'coffee-rails', '4.0.0' and ran bundle update with the gem 'monologue', '~> 0.4.1' in the gem file and it installed.

@vysogot
Copy link

@vysogot vysogot commented Jul 29, 2015

Well, it's July 2015 and it's still an issue with Rails 4.2.2. I must say, +1 for "blogo" which works like a charm.

@vinhnglx
Copy link

@vinhnglx vinhnglx commented Nov 1, 2015

@vysogot

just FYI. I was run monologue on Rails 4.2.4. Here is my configure:

# Gemfile
# Downgrade sass-rails from 5.0 to 4.0.0
gem 'sass-rails', '~> 4.0.0'

# Downgrade coffee-rails from 4.1.0 to 4.0.0
gem 'coffee-rails', '~> 4.0.0'

# Specify version for monologue
gem 'monologue', '~> 0.4.1'

# Fix routing error: The controller-level `respond_to' feature has been extracted to the `responders` gem
gem 'responders', '~> 2.0'

Config assets precompile for social_foundicons fonts in config/initializers/assets.rb

# config/initializers/assets.rb

Rails.application.config.assets.precompile += %w( monologue/foundation_icons/social_foundicons.eot )
Rails.application.config.assets.precompile += %w( monologue/foundation_icons/social_foundicons.woff )
Rails.application.config.assets.precompile += %w( monologue/foundation_icons/social_foundicons.ttf )

And, now it's work well

monologue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.