Conversation
| message += "\n#{File.basename(error.filename)}:#{error.line_number}: #{error.line}" | ||
| message += "\nError: #{error.message}" | ||
| message += "\nUsage: #{error.usage}" unless error.usage.empty? | ||
| message += "\nBacktrace:" |
There was a problem hiding this comment.
This backtrace is really useful when there are bugs in COSMOS itself. Maybe just comment out these lines or make them debug logs?
There was a problem hiding this comment.
Or have the backtrace on only the first error?
There was a problem hiding this comment.
We never want the backtrace on a ConfigParser::Error because those are special errors we're creating.
There was a problem hiding this comment.
There are sometime that we do (mainly because we are using parser.error incorrectly).
Please make sure that these lines in packet_config.rb:
raise parser.error(e)
Include the backtrace.
Also in any of the sub_parsers like limits_response_parser.rb
| message += "\n#{File.basename(error.filename)}:#{error.line_number}: #{error.line}" | ||
| message += "\nError: #{error.message}" | ||
| message += "\nUsage: #{error.usage}" unless error.usage.empty? | ||
| message += "\nBacktrace:" |
There was a problem hiding this comment.
Or have the backtrace on only the first error?
|
2 participants
closes #1255