Vague python traceback when running 'bzr {info,pull}' on an incomplete tree

[Gerald Carter]

Usibg bzr-0.8.2 and the bzrtools plugin. Create a bzr repo.
Publish the tree using the rspush command but cancel
the push early

$ bzr rspush
^C

Now try to retreive the info from the half published tree. You
will get varying errors. For example

bzr: ERROR: Branch <bzrlib.store.revision.knit.KnitRevisionStore
   object at 0x407c366c> has no revision
   <email address hidden>

or

bzr: ERROR: urllib2.HTTPError: HTTP Error 416: Requested
     range not satisfiable
  at /usr/lib/python2.4/urllib2.py line 480
  in http_error_default

It's not all that intuitive that the problem is a half published
tree.

[Gerald Carter (coffeedude.jerry)]

gr....anyway to fix the typo in the subject line in the main report?

[John A Meinel (jameinel)]

Edit Description/Tags link in the upper left.

[John A Meinel (jameinel)]

Canceling rsync while it is running creates a corrupted repository. We should be more aware of this, and exit more gracefully.

1) The repository layout could be tweaked so that rsync also supports our write ordering (index files should come after data files, inventory and revisions should come after knits).

2) Better errors could be given. Though when a repository is randomly corrupted, there is only so much that you can do.