[
https://issues.apache.org/jira/browse/AURORA-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156981#comment-14156981
]
Mark Chu-Carroll commented on AURORA-779:
-----------------------------------------
If the error isn't reproducible, then the stack trace doesn't help that much.
If it is reproducible, then it's easy enough to get the stack when needed.
Dumping stack is a horrible user experience. When there's an error, the user
should get a clean, comprehensible error message. If they don't, it needs
fixing.
Making it easier for us to debug in the unusual error case is no excuse for
making the routine error experience worse.
> v2 client has worse error message than v1
> -----------------------------------------
>
> Key: AURORA-779
> URL: https://issues.apache.org/jira/browse/AURORA-779
> Project: Aurora
> Issue Type: Bug
> Components: Client, Usability
> Reporter: Kevin Sweeney
>
> Copied from a user report at Twitter:
> I had a typo in an aurora config, where I was resolving a mustache variable
> outside of a string:
> {code}
> instances = {{profile.instances}}
> {code}
> where I should have been doing
> {code}
> instances = "{{profile.instances}}"
> {code}
> The error message on the v2 client was:
> {quote}
> Error executing command: Error loading configuration: name 'profile' is not
> defined
> {quote}
> The v1 client gave me a line number:
> {quote}
> File "router.aurora", line 90, in <module>
> instances = {{profile.instances}},
> NameError: name 'profile' is not defined
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
