AssertionError: "get_next() called when there are no chars left" in bzrlib._dirstate_helpers_pyx.Reader.get_next
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
New
|
Undecided
|
Unassigned |
Bug Description
Hello,
I was trying to split a bzr branch into several subbranches. I thought I'd try the answer here:
http://
in that I would use bzr split. Unfortunately, I get an error and a message to email you, which I am now doing. The crash report is attached. The branch is nothing special. The layout is
WorkDocuments/
WorkDocuments/
The command I did was in WorkDocuments, I issued "bzr split SCMTalk." If I'm doing something stupid, I apologize.
Traceback:
Traceback (most recent call last):
File "/usr/lib/
return the_callable(*args, **kwargs)
File "/usr/lib/
ret = run(*run_argv)
File "/usr/lib/
return self.run_
File "/usr/lib/
return self._operation
File "/usr/lib/
self.cleanups, self.func, *args, **kwargs)
File "/usr/lib/
result = func(*args, **kwargs)
File "/usr/lib/
sub_id = containing_
File "/usr/lib/
result = unbound(self, *args, **kwargs)
File "/usr/lib/
entry = self._get_
File "/usr/lib/
return state._get_entry(0, fileid_
File "/usr/lib/
self.
File "/usr/lib/
_read_
File "_dirstate_
File "_dirstate_
File "_dirstate_
File "_dirstate_
File "_dirstate_
AssertionError: get_next() called when there are no chars left
Hi Chris,
This looks ilke a duplicate of bug 450047. Apparently the dirstate file is truncated; I don't know why that has happened. If you remove the .bzr/checkout directory and then run 'bzr checkout' in that directory again you should be ok. Can you think of anything that happened around this time (maybe a machine crash?) that could have caused the file to be truncated? Is this stored on a network or usb disk or anything like that?