Jira (PUP-1631) Wrapped exceptions of functions are still hiding that they were raised in a function

[redmine.exporter (JIRA)]

Title: Message Title

redmine.exporter created an issue   Puppet / PUP-1631 Wrapped exceptions of functions are still hiding that they were raised in a function Issue Type: Bug Assignee: Unassigned Created: 10/Feb/14 7:41 AM Labels: redmine Priority: Normal Reporter: redmine.exporter As noted in #22729 the source of an exception that is thrown in a function, is still completely hidden to the user in the output: <pre> puppet --version 3.3.0 puppet apply -e "notice reject(['a','b'],'b')" Error: reject(): wrong argument type (String; must be a parameterized block. at line 1 on node foo Wrapped exception: reject(): wrong argument type (String; must be a parameterized block. Error: reject(): wrong argument type (String; must be a parameterized block. at line 1 on node foo </pre> There is no way that I can see that this exception was actually raised in the function itself and I need to use `--trace` to see the actual source of the problem. Also the actual Error and the wrapped exception output look identical to me and it makes no sense to have this output doubled. As a user I'd like to be able to: 1. See the message of the raised exception 2. See the actual source of the raised exception (in the case above the function reject). Otherwise we should not output the wrapped exception at all, because it makes the output very confusing. Add Comment   This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.