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

get error Command failed with status (2) when run 'rake diagram:all' #88

Open
karinelisabeth opened this issue Jan 31, 2015 · 7 comments

Comments

@karinelisabeth
Copy link

Hi, I have installed railroady, but I get the error: 'Command failed with status (2)' when run 'rake diagram:all'. I am using rails v4.2.0. It creates the /doc file without any problems.

Here is the full error message:

sh: -c: line 0: unexpected EOF while looking for matching `''
sh: -c: line 1: syntax error: unexpected end of file
rake aborted!
Command failed with status (2): [railroady -lamM | sed -E 's/\x1B[([0-9]{1...]

@preston
Copy link
Owner

preston commented Jan 31, 2015

That's odd. What's the full output?

@karinelisabeth
Copy link
Author

Thanks for quick reply! Here is the full output:

$ rake diagram:all --trace
** Invoke diagram:all (first_time)
** Invoke diagram:setup:create_new_doc_folder_if_needed (first_time)
** Execute diagram:setup:create_new_doc_folder_if_needed
** Invoke diagram:models:complete (first_time)
** Execute diagram:models:complete
Generating /Users/em/Documents/Eli's\ folder/ruby\ &\ rails/1\ -\ ruby\ &\ rails/3\ -\ rails\ to\ do\ application/ToDo_App/doc/models_complete.svg
railroady -lamM | sed -E 's/\x1B[([0-9]{1,2}(;[0-9]{1,2})?)?[m|K]//g' | dot -Tsvg > /Users/em/Documents/Eli's\ folder/ruby\ &\ rails/1\ -\ ruby\ &\ rails/3\ -\ rails\ to\ do\ application/ToDo_App/doc/models_complete.svg
sh: -c: line 0: unexpected EOF while looking for matching '' sh: -c: line 1: syntax error: unexpected end of file rake aborted! Command failed with status (2): [railroady -lamM | sed -E 's/\x1B\[([0-9]{1...] /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/file_utils.rb:66:inblock in create_shell_runner'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/file_utils.rb:57:in call' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/file_utils.rb:57:insh'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/file_utils_ext.rb:37:in sh' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/railroady-1.3.0/tasks/railroady.rake:65:inblock (3 levels) in <top (required)>'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:240:in call' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:240:inblock in execute'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:235:in each' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:235:inexecute'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:179:in block in invoke_with_call_chain' /Users/em/.rbenv/versions/2.1.5/lib/ruby/2.1.0/monitor.rb:211:inmon_synchronize'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:172:in invoke_with_call_chain' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:201:inblock in invoke_prerequisites'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:199:in each' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:199:ininvoke_prerequisites'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:178:in block in invoke_with_call_chain' /Users/em/.rbenv/versions/2.1.5/lib/ruby/2.1.0/monitor.rb:211:inmon_synchronize'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:172:in invoke_with_call_chain' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/task.rb:165:ininvoke'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/application.rb:150:in invoke_task' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/application.rb:106:inblock (2 levels) in top_level'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/application.rb:106:in each' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/application.rb:106:inblock in top_level'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/application.rb:115:in run_with_threads' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/application.rb:100:intop_level'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/application.rb:78:in block in run' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/application.rb:176:instandard_exception_handling'
/Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/lib/rake/application.rb:75:in run' /Users/em/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/rake-10.4.2/bin/rake:33:in<top (required)>'
/Users/em/.rbenv/versions/2.1.5/bin/rake:23:in load' /Users/em/.rbenv/versions/2.1.5/bin/rake:23:in

'
Tasks: TOP => diagram:all => diagram:models:complete

@preston
Copy link
Owner

preston commented Feb 4, 2015

Hmm ... Windows I kindof a mystery to me so I'm not sure about this one, sorry!

@lingyan1002
Copy link

Excuse me, I encountered a problem when I ran "rake diagram:all", I found that the directory of my project is not consistent with the default directory, how can I solve this problem?

@preston
Copy link
Owner

preston commented Jul 18, 2016

I think you have a different issue than the OP, and I would suggest going to a more consistent structure. Other than being a good convention in general, Railroady does expect a standard directory structure.

@lingyan1002
Copy link

Is there any other solution? because my project is made up of many different modules and it is not suitable to revise the directory

@preston
Copy link
Owner

preston commented Jul 22, 2016

Most likely you'd have to fork and make some code changes. You could trying using symlinks, but I'm not sure that'll work.

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

No branches or pull requests

3 participants