How can I disable the trace in rake tasks?
I'm not sure when this started, but whenever I run a rake task in Rails:
$ rake routes
Before it prints the routes, it shows the trace:
** Invoke routes (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute routes
I thought those invoke/execute statements would only appear if I added --trace to my command, but it happens for all of my rake tasks (db create/migrate, Capistrano, etc.)
Is there a way to disable the trace functionality? Is there a configuration file in Rails that might be enabling trace that I'm unaware of?
ruby-on-rails rake
asked Nov 20 '18 at 13:38
ardavisardavis
6,10494299
add a comment |
I'm not sure when this started, but whenever I run a rake task in Rails:
$ rake routes
Before it prints the routes, it shows the trace:
** Invoke routes (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute routes
I thought those invoke/execute statements would only appear if I added --trace to my command, but it happens for all of my rake tasks (db create/migrate, Capistrano, etc.)
Is there a way to disable the trace functionality? Is there a configuration file in Rails that might be enabling trace that I'm unaware of?
ruby-on-rails rake
asked Nov 20 '18 at 13:38
ardavisardavis
6,10494299
add a comment |
I'm not sure when this started, but whenever I run a rake task in Rails:
$ rake routes
Before it prints the routes, it shows the trace:
** Invoke routes (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute routes
I thought those invoke/execute statements would only appear if I added --trace to my command, but it happens for all of my rake tasks (db create/migrate, Capistrano, etc.)
Is there a way to disable the trace functionality? Is there a configuration file in Rails that might be enabling trace that I'm unaware of?
ruby-on-rails rake
asked Nov 20 '18 at 13:38
ardavisardavis
6,10494299
I'm not sure when this started, but whenever I run a rake task in Rails:
$ rake routes
Before it prints the routes, it shows the trace:
** Invoke routes (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute routes
I thought those invoke/execute statements would only appear if I added --trace to my command, but it happens for all of my rake tasks (db create/migrate, Capistrano, etc.)
Is there a way to disable the trace functionality? Is there a configuration file in Rails that might be enabling trace that I'm unaware of?
ruby-on-rails rake
ruby-on-rails rake
asked Nov 20 '18 at 13:38
ardavisardavis
6,10494299
asked Nov 20 '18 at 13:38
ardavisardavis
6,10494299
asked Nov 20 '18 at 13:38
ardavisardavis
6,10494299
asked Nov 20 '18 at 13:38
ardavisardavis
6,10494299
asked Nov 20 '18 at 13:38
ardavisardavis
6,10494299
6,10494299
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The problem has been tracked down to a custom gem that implements a Capistrano Plugin. The gem allows for a different version control system to be used with Capistrano other than the ones they provide (Git, SVN, etc.).
The ultimate issue was that capistrano/lib/capistrano/all.rb has this line:
Rake.application.options.trace = true
This file was being loaded with the Capistrano Plugins, but the default ones are not required until used in the Capfile. When we created a custom gem with a new plugin, we simply added the new gem to our application's Gemfile, which loads the files by default. So our plugin file looked like this:
# custom_gem/lib/capistrano/scm/custom_vc.rb
require 'capistrano/scm/plugin'
class Capistrano::SCM::CustomVC < Capistarno::SCM::Plugin
# ... Mimic the capistrano/lib/capistrano/scm/git.rb in the Capistrano gem.
end
The top line that requires capistrano/scm/plugin was ultimately requiring the capistrano-lib/capistrano/all.rb that was setting trace to be on for all Rake tasks.
The solution was to simply add require: false to our Gemfile for the custom gem.
# Gemfile
group :development do
gem 'capistrano_custom_vc', require: false
end
answered Nov 20 '18 at 15:10
ardavisardavis
6,10494299
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394288%2fhow-can-i-disable-the-trace-in-rake-tasks%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The problem has been tracked down to a custom gem that implements a Capistrano Plugin. The gem allows for a different version control system to be used with Capistrano other than the ones they provide (Git, SVN, etc.).
The ultimate issue was that capistrano/lib/capistrano/all.rb has this line:
Rake.application.options.trace = true
This file was being loaded with the Capistrano Plugins, but the default ones are not required until used in the Capfile. When we created a custom gem with a new plugin, we simply added the new gem to our application's Gemfile, which loads the files by default. So our plugin file looked like this:
# custom_gem/lib/capistrano/scm/custom_vc.rb
require 'capistrano/scm/plugin'
class Capistrano::SCM::CustomVC < Capistarno::SCM::Plugin
# ... Mimic the capistrano/lib/capistrano/scm/git.rb in the Capistrano gem.
end
The top line that requires capistrano/scm/plugin was ultimately requiring the capistrano-lib/capistrano/all.rb that was setting trace to be on for all Rake tasks.
The solution was to simply add require: false to our Gemfile for the custom gem.
# Gemfile
group :development do
gem 'capistrano_custom_vc', require: false
end
answered Nov 20 '18 at 15:10
ardavisardavis
6,10494299
add a comment |
The problem has been tracked down to a custom gem that implements a Capistrano Plugin. The gem allows for a different version control system to be used with Capistrano other than the ones they provide (Git, SVN, etc.).
The ultimate issue was that capistrano/lib/capistrano/all.rb has this line:
Rake.application.options.trace = true
This file was being loaded with the Capistrano Plugins, but the default ones are not required until used in the Capfile. When we created a custom gem with a new plugin, we simply added the new gem to our application's Gemfile, which loads the files by default. So our plugin file looked like this:
# custom_gem/lib/capistrano/scm/custom_vc.rb
require 'capistrano/scm/plugin'
class Capistrano::SCM::CustomVC < Capistarno::SCM::Plugin
# ... Mimic the capistrano/lib/capistrano/scm/git.rb in the Capistrano gem.
end
The top line that requires capistrano/scm/plugin was ultimately requiring the capistrano-lib/capistrano/all.rb that was setting trace to be on for all Rake tasks.
The solution was to simply add require: false to our Gemfile for the custom gem.
# Gemfile
group :development do
gem 'capistrano_custom_vc', require: false
end
answered Nov 20 '18 at 15:10
ardavisardavis
6,10494299
add a comment |
The problem has been tracked down to a custom gem that implements a Capistrano Plugin. The gem allows for a different version control system to be used with Capistrano other than the ones they provide (Git, SVN, etc.).
The ultimate issue was that capistrano/lib/capistrano/all.rb has this line:
Rake.application.options.trace = true
This file was being loaded with the Capistrano Plugins, but the default ones are not required until used in the Capfile. When we created a custom gem with a new plugin, we simply added the new gem to our application's Gemfile, which loads the files by default. So our plugin file looked like this:
# custom_gem/lib/capistrano/scm/custom_vc.rb
require 'capistrano/scm/plugin'
class Capistrano::SCM::CustomVC < Capistarno::SCM::Plugin
# ... Mimic the capistrano/lib/capistrano/scm/git.rb in the Capistrano gem.
end
The top line that requires capistrano/scm/plugin was ultimately requiring the capistrano-lib/capistrano/all.rb that was setting trace to be on for all Rake tasks.
The solution was to simply add require: false to our Gemfile for the custom gem.
# Gemfile
group :development do
gem 'capistrano_custom_vc', require: false
end
answered Nov 20 '18 at 15:10
ardavisardavis
6,10494299
The problem has been tracked down to a custom gem that implements a Capistrano Plugin. The gem allows for a different version control system to be used with Capistrano other than the ones they provide (Git, SVN, etc.).
The ultimate issue was that capistrano/lib/capistrano/all.rb has this line:
Rake.application.options.trace = true
This file was being loaded with the Capistrano Plugins, but the default ones are not required until used in the Capfile. When we created a custom gem with a new plugin, we simply added the new gem to our application's Gemfile, which loads the files by default. So our plugin file looked like this:
# custom_gem/lib/capistrano/scm/custom_vc.rb
require 'capistrano/scm/plugin'
class Capistrano::SCM::CustomVC < Capistarno::SCM::Plugin
# ... Mimic the capistrano/lib/capistrano/scm/git.rb in the Capistrano gem.
end
The top line that requires capistrano/scm/plugin was ultimately requiring the capistrano-lib/capistrano/all.rb that was setting trace to be on for all Rake tasks.
The solution was to simply add require: false to our Gemfile for the custom gem.
# Gemfile
group :development do
gem 'capistrano_custom_vc', require: false
end
answered Nov 20 '18 at 15:10
ardavisardavis
6,10494299
answered Nov 20 '18 at 15:10
ardavisardavis
6,10494299
answered Nov 20 '18 at 15:10
ardavisardavis
6,10494299
answered Nov 20 '18 at 15:10
ardavisardavis
6,10494299
6,10494299
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53394288%2fhow-can-i-disable-the-trace-in-rake-tasks%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
