"Bad message kind byte: '\xfb'" from server while pushing to Launchpad
Bug #622844 reported by
Eduardo Mucelli Rezende Oliveira
This bug report is a duplicate of:
Bug #532550: bzr error: Bad message kind byte: '\\x1d'.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Bazaar |
Incomplete
|
High
|
Unassigned | ||
Bug Description
bzr: ERROR: bzrlib.
~/.cache/
Revision history for this message
| Eduardo Mucelli Rezende Oliveira (eduardo-mucelli) wrote | #1 |
Revision history for this message
| Andrew Bennetts (spiv) wrote | #2 |
| summary: |
- Crash when commiting to Launchpad + "Bad message kind byte: '\xfb'" from server while pushing to Launchpad |
| tags: |
added: hpss removed: commit crash launchpad |
| Changed in bzr: | |
| importance: | Undecided → High |
| status: | New → Incomplete |
Revision history for this message
| Eduardo Mucelli Rezende Oliveira (eduardo-mucelli) wrote | #3 |
To post a comment you must log in.
This is perhaps a duplicate of bug 532550. It appears that while sending the new revisions to the server (with an 'insert_stream' HPSS call) the server has seen a corruption in the stream from the client and aborted the stream with this error.
Like 532550 the cause is a mystery. Is there anything unusual about the branch being pushed? Is it very large? Are there non-ascii filenames in the new revisions? (I'd be surprised if committed filenames were the culprit, but that was a theory proposed for 532550, so worth checking).
And is this error reproducible?