bzr crashed when pushing to launchpad

[Sergey Petrunia]

I've tried a to make a push to a launchpad tree (with one changeset) and got this crash:

$ bzr push
Using saved push location: bzr+ssh://bazaar.launchpad.net/~maria-captains/maria/5.3-subqueries-mwl90/
\ 1348KB 2KB/s | Fetching revisions:Inserting missing keys

bzr: ERROR: bzrlib.errors.ErrorFromSmartServer: Error received from smart server: ('error', "Generic bzr smart protocol error: Bad message kind byte: 'A'")

*** Bazaar has encountered an internal error. This probably indicates a
    bug in Bazaar. You can help us fix it by filing a bug report at
        https://bugs.launchpad.net/bzr/+filebug
    attaching the crash file
        /home/psergey/.cache/crash/bzr-20100608142402-9074.crash
    and including a description of the problem.

    The crash file is plain text and you can inspect or edit it to remove
    private information.

If I retry the push, I get this error:

Unable to obtain lock lp-69989648:///~maria-captains/maria/5.3-subqueries-mwl90/.bzr/branch/lock
held by <email address hidden> on host crowberry [process #25177]
locked 1 minute, 37 seconds ago

[Sergey Petrunia (sergefp)]

I've now retried doing the push (after doing bzr break-lock on the launchpad repo) and it went without any problem. The tree I'm pushing from, bzr version, etc - all are the same but the issue went away for some reason.

[Andrew Bennetts (spiv)]

I'm glad that pushing again solved your immediate problem.

This is a bit mysterious. The server is reporting that the stream it received was corrupted, and the traceback shows this happened while your bzr client was inserting new revisions into the remote repository. In that case it's strange that the next push you did (after the break-lock) succeeded, because in theory the remote and local repositories and branches should have been in the exact same state as for the first push, so the network conversation should have been identical.

So it appears that there was some transient condition that corrupted your stream, something outside of bzr. Potentially it might be a hardware issue corrupting your memory, or something rare like that :/

I've added launchpad-code to this bug because this error message originates on the server, and it is possible that there's a crash log or some other clue on the server that the launchpad-code team can find that would shed light on this.

[Tim Penhey (thumper)]

No info on the codehosting side that I can find.