XML-RPC OOPS ids are not exposed to users of bzr making failure diagnosis tedious
Bug #613806 reported by
Jonathan Lange
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lazr.sshserver |
Triaged
|
High
|
Anna Widajewicz | ||
| Ubuntu |
Fix Released
|
Undecided
|
Anna Widajewicz | ||
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.
Related branches
| Changed in launchpad: | |
| importance: | Undecided → High |
Revision history for this message
| Martin Pool (mbp) wrote | #1 |
Revision history for this message
| Robert Collins (lifeless) wrote | #2 |
| 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 |
| affects: | launchpad → lazr.sshserver |
| Changed in ubuntu: | |
| status: | New → Fix Released |
| assignee: | nobody → Anna Widajewicz (anna123456) |
| Changed in lazr.sshserver: | |
| assignee: | nobody → Anna Widajewicz (anna123456) |
To post a comment you must log in.
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.