On 6 April 2011 17:38, Robert Collins <email address hidden> wrote:
> On the server side, we shouldn't record an OOPS for this; its something
> clients can trivially cause (via hacking or mistakes).
Well, that's true, but on the other hand it seems like in this case it
is happening because of a fault in Launchpad, or perhaps lplib. In
that sense it's a bit like other 400-type errors.
On 6 April 2011 17:38, Robert Collins <email address hidden> wrote:
> On the server side, we shouldn't record an OOPS for this; its something
> clients can trivially cause (via hacking or mistakes).
Well, that's true, but on the other hand it seems like in this case it
is happening because of a fault in Launchpad, or perhaps lplib. In
that sense it's a bit like other 400-type errors.