Error: <stdin>:1: syntax error near line 1 #41
Comments
|
Same issue with Ruby 2. |
|
Ah, my problem seems to be something like this: what is being output by railroady has a bad starting line. If we can get rid of that, we are good to go. (snipped output) (snipped...) This was runnable: railroady -ilamM | grep -v schema_migrations | dot -Tsvg > doc/models_complete.svg So, my final script for my Jenkins job to do this became: #!/bin/bash
set -e
# initialize rbenv
source ~/.bash_profile
function railroad_diagram {
foreman run -e .env_test railroady $1 | grep -v schema_migrations
}
function railroad_diagram_models {
railroad_diagram "-ilamM" | dot -T$1 > doc/models_complete.$1
railroad_diagram "-bilamM" | dot -T$1 > doc/models_brief.$1
}
function railroad_diagram_controllers {
railroad_diagram "-ilC" | dot -T$1 > doc/controllers_complete.$1
railroad_diagram "-bilC" | dot -T$1 > doc/controllers_brief.$1
}
for diagram_format in svg png; do
railroad_diagram_models $diagram_format
railroad_diagram_controllers $diagram_format
done |
|
Ran into a similar situation. Added this to |
|
Same issue here with ruby 2.1.2p95. @evadne solution didn't work :( |
|
@ocolot You just need to hook the logger and see if when |
|
Same problem here w/ ruby 2.0.0p481 , @evadne solution didn't work. |
|
I had a similar issue and found that the first part of the pipe sequence:
this bit:
had extraneous input above what railroady was expecting would come out. In my case I like to see SQL in my logs in dev and had this line in my development.rb:
And that was logging some db queries into the roady output. Using @evadne 's recommendation I put this in my development.rb and all is now well: |
|
I get that problem when there is a forbidden character somewhere in any names. For the specific case of using it in decision trees, this generally fixes it for me: Would be great if the error were clearer as to where the problem is though. |
When I run
diagram:all, and then even justI get an error:
so with trace,
Any suggestions? Thanks for your hard work on this.
The text was updated successfully, but these errors were encountered: