8

I've written a very simple rake task to try and locate the source of this problem.

namespace :foo do
 task bar: :environment do
  puts 'RUNNING'
 end
end

When executed in the console rake foo:bar the output is:

RUNNING
RUNNING

This occurs when I execute any rake task. Has anyone encountered anything like this before?

EDIT

The above rake task is all that is written in that .rake file.

Here is the Rakefile currently being used.

require File.expand_path('../config/application', __FILE__)

OurApp::Application.load_tasks

Also here is the output from running a --trace.

** Invoke foo:bar (first_time)
** Invoke environment (first_time)
** Execute environment
Hostname is: ourhost
** Execute foo:bar
RUNNING
RUNNING
Broc Broccoli
  • 191
  • 3
  • 11
  • The `rails_12factor` causes double log entries. If you have it installed make sure you're only loading it in the :production environment: `gem 'rails_12factor', group: :production` – infused Mar 08 '16 at 19:00
  • we don't use rails_12factor, thanks for the tip though! – Broc Broccoli Mar 08 '16 at 19:04
  • can you please provide additional code. Are you requiring `rake` or a rake file again possibly? googling "rake executing twice" has a lot of possible reasons why this would happen but most of them seem to boil down to multiple require or initialization where they are not needed. – engineersmnky Mar 08 '16 at 19:28
  • 3
    Try running `rake foo:bar --trace` which displays the order of tasks. That might give you an idea of whats calling the particular task twice. – Dharam Gollapudi Mar 08 '16 at 19:34
  • From the trace the task seems to be run only once. Can you add a second puts, e.g. `puts "STILL RUNNING"` and show us the output so that we can rule out a possible double echoing to the console? – Matouš Borák Mar 09 '16 at 06:20
  • Hope this discussion can help: http://stackoverflow.com/questions/31622304/why-is-my-rake-task-running-twice-in-my-test – kucaahbe Dec 19 '16 at 14:31

4 Answers4

6

This is reproducible in a brand new app. The problem disappears if you do not pass the :environment parameter to the rake task.

I traced the issue to ~/.rvm/rubies/ruby-2.2.2/lib/ruby/2.2.0/rake/task.rb where we hit the enhance() method twice for this rake task:

[99, 108] in /Users/inovakov/.rvm/rubies/ruby-2.2.2/lib/ruby/2.2.0/rake/task.rb
    99:     # Enhance a task with prerequisites or actions.  Returns self.
   100:     def enhance(deps=nil, &block)
   101:       byebug if self.to_s.include? 'foo'
   102:       @prerequisites |= deps if deps
   103:       @actions << block if block_given?
=> 104:       self
   105:     end
   106: 
   107:     # Name of the task, including any namespace qualifiers.
   108:     def name
(byebug) @actions
[#<Proc:0x007ff492701aa0@/Users/inovakov/source/test_app/lib/tasks/foo.rake:4>, #<Proc:0x007ff4920d3f70@/Users/inovakov/source/test_app/lib/tasks/foo.rake:4>]

Between the first and the second time we hit this method we initialise the environment - in this case app/config/environments/development.rb.

If we have two outputs in the rake task we see them both:

bash-3.2$ bundle exec rake foo:bar --trace
** Invoke foo:bar (first_time)
** Invoke environment (first_time)
** Execute environment
Hostname is: localhost
** Execute foo:bar
RUNNING
STILL RUNNING
RUNNING
STILL RUNNING

(I know this is not an answer but I don't have comment privileges yet and this could hopefully help the discussion.)

31piy
  • 23,323
  • 6
  • 47
  • 67
Ivaylo Novakov
  • 775
  • 6
  • 18
6

There are plenty of reasons why a Rake task could be running twice, and in this specific case I think it could have to do with the Rake environment loading more than once, as the question linked by @kucaahbe suggests.

I actually got here looking for help myself but my issue was different and I managed to find the answer. Don't think it will help this particular issue but I'll leave it here too.

Make sure your Rake environment is loading only once

Following the question linked by @kucaahbe, it suggests this would happen if your environment is loading and initializing Rake twice.

In the context a Rake task runs rake has already been required and initialized, so make sure your task does not include the following lines:

require 'rake'
...
Rake.application.init
Rake.application.load_rakefile

In this specific case the task does not seem to be doing anything of the sort, so I would check other tasks or the Rakefile for something forcing the Rake context to be loaded twice.

Clear pre-existing tasks before redefining them

Just had this issue due to a gem creating a Rake task with the same name.

For instance, if you declare the following task in a Rails application:

namespace :assets do
  task :precompile do
    puts "Hello"
  end
end

and run rake assets:precompile:

...
I, [2017-07-31T11:25:09.498897 #9455]  INFO -- : Writing /home/pfac/...css.gz
Hello
Hello

But if you use Rake::Task#clear:

namespace :assets do
  task(:precompile).clear
  task :precompile do
    puts "Hello"
  end
end

it disables any pre-existing behaviour and prints only Hello.

I don't think this option solves this particular issue, unless @broc-broccoli has been defining other foo:bar rake tasks.

Anyway, hope this helps.

pfac
  • 710
  • 7
  • 13
0

For me my rake environnement was loading twice in my rails app because of the presence in my test file of :

setup do
  MyApp::Application.load_tasks
end

I removed it and the task was invoked once.

Hope it can help.

Sorry for my english.

Julien
  • 1
0

In my case, I've explicitly added tasks loading from the Rakefile:

Rake.add_rakelib 'lib/tasks'

So removing so case lines may help.

Малъ Скрылевъ
  • 16,187
  • 5
  • 56
  • 69