-
Notifications
You must be signed in to change notification settings - Fork 16
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
Show on which line an error occurred #16
Comments
Can you update the the newest HEAD (i exposed the debug logging via the CLI now) Then run As far as line numbers go, i will need to look a bit more on the best way to do that |
Sure. Although it looks like I needed to actually specify 'pry' in my Gemfile: % bundle exec yamllint hieradata/env/qa.yaml -D
bundler: failed to load command: yamllint
LoadError: cannot load such file -- pry Is it listed as a dependency? Also, I see a metric ton of these:
Is that possibly what I'm after? |
Actually, I see here... but it's still not clear:
The YAML for that section has the following: bar::roles: [web, worker]
bar::log_level: DEBUG
bar::media_root: /tmp/
bar::rabbitmq_host: *rabbitmq_host
bar::db_host: *db_host
foo::log_level: DEBUG
foo::rabbitmq_host: *rabbitmq_host
blah::bind_address: 0.0.0.0:8080
blah::log_level: DEBUG
blah::redis_database: 5 Does it not like aliases? |
Sorry about that! i will fix that
That is possible, i didn't test for that. Let me do some poking around. Might not like the |
With the following i get no errors with what is in HEAD
|
Strange. That's where the error is popping up in the debug output. I'd be interesting in that line numbering capability here, then. In case it matters, this is running ruby 2.3.1. |
Will look at line numbering |
Let me know if I can get you any more data. |
Looks like this may have actually been a problem with the alias and should be fixed by #36. |
Using the git version, I get this very unhelpful message:
Looking in the file, it's not immediately obvious where this occurs; I can't even find a key named debug. Any ideas?
The text was updated successfully, but these errors were encountered: