XML-RPC OOPS ids are not exposed to users of bzr making failure diagnosis tedious

Bug #613806 reported by Jonathan Lange on 2010-08-05
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lazr.sshserver
High
Unassigned

Bug Description

When things go seriously wrong in the XML-RPC server, it generates an OOPS. This can cause errors to appear on the bzr client. However, those errors do not mention the OOPS, and in general there's no way of matching them to the XML-RPC error.

The codehosting SSH server should get OOPS codes from the XML-RPC server and forward them to the client.

Changed in launchpad:
importance: Undecided → High
Martin Pool (mbp) wrote :

Although the original description is about the xmlrpc server, bzr lp-serve can now also generate oopses, and it should be able to do the same thing internally.

Robert Collins (lifeless) wrote :

That deserves a separate bug because one is triggered by a remote error code, and the other an internal exception: flow control in the former case will be quite different to the latter. (I suspect).

summary: - SSH server should forward OOPS code to bzr client
+ XML-RPC OOPS ids are not exposed to users of bzr making failure
+ diagnosis tedious
Colin Watson (cjwatson) on 2015-01-14
affects: launchpad → lazr.sshserver
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers