Issue #2377 has been updated by Luke Kanies.
Brice Figureau wrote: > When we raise this error in the client, is it possible to replace the > stacktrace by one we'd have from the server? > This way we'd display a meaningful stacktrace on the client (more meaningful > than something ending in P::I::Rest#deserialize). I looked into this, I think, and I couldn't find an easy way to return anything other than the error itself. I suppose that error could be serialized content that could be deserialized and printed on the client. ---------------------------------------- Feature #2377: Add a message in the client error handler if the error comes from the master http://projects.reductivelabs.com/issues/2377 Author: Brice Figureau Status: Ready for Testing Priority: Normal Assigned to: Brice Figureau Category: plumbing Target version: 0.25.0 Complexity: Trivial Affected version: 0.24.8 Keywords: The idea is to reduce the number of round-trip in tickets and inform the user that the error originated in the master and not in the client. Something along the line of: here the original error messge This error has occurred on the puppetmaster. If you want to get more useful information, please have a look in your puppetmaster logs. Running your puppetmaster with --trace will help the developer locate and fix the issue. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
