On 2014-02-07 21:56, Sean Kelly wrote:
I was mostly surprised that the stack trace was written back to the client. I'd expect something like that in a log on the server side. I do see how it would be convenient to have a stack trace included in a bug report, but if this feature is disabled in release mode then you can't rely on it anyway. I'd just always be checking the logs (where I'd hope the stack trace would always be written).
Ruby on Rails always writes the stack trace to the log. In development mode it will also render it to the client. In production mode we use a plugin that sends an email when an exception occurs. The email will contain the full stack trace, environment variables and some other data about the request that failed.
BTW, you can do a lot more with HTML than plain text (log files). -- /Jacob Carlborg
