Merge lp:~jameinel/bzr/2.0.1-btree-better-errors into lp:bzr/2.0
Proposed by
John A Meinel
Status: | Merged |
---|---|
Merged at revision: | not available |
Proposed branch: | lp:~jameinel/bzr/2.0.1-btree-better-errors |
Merge into: | lp:bzr/2.0 |
Diff against target: |
63 lines 1 file modified
bzrlib/_btree_serializer_pyx.pyx (+6/-8) |
To merge this branch: | bzr merge lp:~jameinel/bzr/2.0.1-btree-better-errors |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Robert Collins (community) | Approve | ||
Review via email: mp+12759@code.launchpad.net |
To post a comment you must log in.
In some of my other work that I've been doing I ended up feeding some bogus data to the btree serializer.
In the 'process_line()' function, we declare that returning -1 indicates an exception is set, however there are several code paths that return -1 during an error without raising an exception. In those cases I end up with:
Traceback (most recent call last):
File "<string>", line 1, in <module>
SystemError: error return without exception set
Rather than getting a nice parse error sort of condition.
So I fixed all of those to be nicer. I figure this is trivial enough to go into 2.0.1 (pre-emptive bug fix :).