I started having the same problem this evening. It seems to be related to Rack 1.3.4. I fixed it by adding this to my Gemfile: gem ‘rack’, ‘1.3.3’ Then running: bundle update rack Incidentally, I tried Bozhidar’s suggestion before this, but to no avail.
on my Mac OS X 10.6 I did this to install the 2.8.1 gem, which worked perfectly with my MacPorts mysql5-server: sudo env ARCHFLAGS=”-arch x86_64″ gem install mysql
bundle exec executes a command in the context of your bundle. That means it uses the gems specified in your Gemfile. Much of the time, running bundle exec rake foo has the same results as if you just ran rake foo, especially if you have the same gems installed systemwide as in your Gemfile. However, … Read more
Make sure you’re entering “bundle” update, if you have the bundler gem installed. bundle update If you don’t have bundler installed, do gem install bundler.
Just to follow up on this old topic; here’s what I think a current Rakefile (since a long ago) should do there. It’s an upgraded and bugfixed version of the current winning answer (hgimenez): desc “Testing environment and variables” task :hello, [:message] => :environment do |t, args| args.with_defaults(:message => “Thanks for logging on”) puts “Hello … Read more
Figured it out, the task should look like: namespace :test do task :new_task => :environment do puts Parent.all.inspect end end Notice the => :environment dependency added to the task
I know two ways to do this: This will reset your database and reload your current schema with all: rake db:reset db:migrate This will destroy your db and then create it and then migrate your current schema: rake db:drop db:create db:migrate All data will be lost in both scenarios.
I just ran into this as well. This is due to ActiveRecord 4.2.0.beta4 passing a parameter to Arel::Nodes::BindParam.new. Arel 6.0.0 was just released today. In this version, BindParam does not accept any parameters in it’s initalizer. ActiveRecord has already fixed this on the master branch. Until beta5 is released you’ll need to lock your Gemfile … Read more
If you define a rake task that already exists, its execution gets appended to the original task’s execution; both tasks will be executed. If you want to redefine a task you need to clear the original task first: Rake::Task[“db:test:prepare”].clear It’s also useful to note that once a task has been executed in rake, it won’t … Read more
bundle config set –local path ‘vendor/cache’ generally fixes it as that is the more common problem. Basically, your bundler path configuration is messed up. See their documentation (first paragraph) for where to find those configurations and change them manually if needed.