Fwd: story of a failure

[Gustavo Niemeyer]

This went private on Friday, by mistake:

---------- Forwarded message ----------
From: Gustavo Niemeyer <gustavo at niemeyer.net>
Date: Fri, Apr 26, 2013 at 7:27 PM
Subject: Re: story of a failure
To: roger peppe <rogpeppe at gmail.com>


On Fri, Apr 26, 2013 at 6:17 PM, roger peppe <rogpeppe at gmail.com> wrote:
> Agreed that that error is less verbose and probably fine for many purposes,
> but from the point of view of diagnosing this problem, it also throws away
> important information - are we seeing this error when talking to an existing
> connection, or when making a new one?
>
> I am concerned that currently by default we add no context to errors, (...)

There might be a mix up between the idea of an error message with the
idea of a verbose log that shows everything that happens in the server
at the time an error happens. The purpose of an error message, with
traceback or not, is to say something bad happened, and provide some
guidance towards what it was.  It's not provide so much information
that you can infer the whole context on the server from it.

Have you had a chance to observe the concept of OOPS that Launchpad
uses?  When something breaks, it says so and provides a unique id that
may be used to get detailed information about what the server was up
to when that error was found.


gustavo @ http://niemeyer.net


-- 

gustavo @ http://niemeyer.net