-
Notifications
You must be signed in to change notification settings - Fork 142
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
Error while trying to run rake task #104
Comments
Could you try running the command string manually from the command line and see if that helps to troubleshoot? This doesn't look familiar. |
I'm getting the same, even from directly triggering it:
Graphviz doesn't like digits in the beginning. |
I am getting similar errors (using brew graphviz 2.38.0_1)
|
Also on:
|
I see this too - funny - it works for me in some rails projects but not others ... here's me splitting the command into three components:
|
Clue. Something in the Railroady code seems to be outputting this line first, which causes dot to fail:
|
#116 should fix this. |
I am running in to this issue as well. Some work, some don't, like @tansaku says. |
@roeintense Right, it depends on Rails logging and maybe some other settings. Try the fork in #116 (could we please get that merged?). |
Seems this all relates to ActiveRecord logging. Simple solution that worked for me was to set the ActiveRecord logger to Rails.application.configure do
config.log_level = :debug
config.active_record.logger = Logger.new(STDOUT)
config.active_record.logger.level = config.log_level
if $0 =~ /(rake|railroady|erd)$/
config.active_record.logger = nil
end
end |
@marnen once that's merged, it may help. However, if there is an AR logger and the log level is |
@joelvh Are you saying that AR logging in Rails doesn't necessarily come through the Rails logger? That's the only case I could think of in which your last comment would be accurate. |
Are folks ok with merging in PR #116? |
Output from logging is what is tripping it up for me as well, so silencing the logger seems like an okay solution. |
Silence logger when getting schema. [#104]
ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14]
Rails 4.1.11
The text was updated successfully, but these errors were encountered: