On Thu, Jul 06, 2006 at 04:40:48AM -0000, Andrew Bennetts wrote:
> This really looks to be a bug on the server side (i.e. Launchpad),
> rather than bzr. Either Launchpad should accept authors without @, or
> it should give a useful error message rather than tripping over an
> assertion. I'm reassigning this to launchpad-bazaar.
I think there's a bug both on the server side in Launchad and in the
bzr plugin. It's definitely a bug in Launchpad, you shouldn't see such
a traceback, you should get a Fault instance back. I have a branch
which allows for testing XMLRPC better so that we can ensure this isn't
broken, and we also need to pull in a fix from Zope3 upstream.
assignee bjornt
After that's fixed, the bzr plugin might have to be changed to catch all
the Fault instances to provide better error messages.
On Thu, Jul 06, 2006 at 04:40:48AM -0000, Andrew Bennetts wrote:
> This really looks to be a bug on the server side (i.e. Launchpad),
> rather than bzr. Either Launchpad should accept authors without @, or
> it should give a useful error message rather than tripping over an
> assertion. I'm reassigning this to launchpad-bazaar.
I think there's a bug both on the server side in Launchad and in the
bzr plugin. It's definitely a bug in Launchpad, you shouldn't see such
a traceback, you should get a Fault instance back. I have a branch
which allows for testing XMLRPC better so that we can ensure this isn't
broken, and we also need to pull in a fix from Zope3 upstream.
assignee bjornt
After that's fixed, the bzr plugin might have to be changed to catch all
the Fault instances to provide better error messages.