[qannotate] Got traceback using latest bzr.dev
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QBzr |
Fix Released
|
High
|
Alexander Belchenko |
Bug Description
Got the following traceback when I ran qannotate on latest bzr.dev NEWS file with latest bzr.dev:
---
bzr.dev szilveszter$ bzr qannotate NEWS
bzr: ERROR: bzrlib.
Traceback (most recent call last):
File "/Library/
return run_bzr(argv)
File "/Library/
ret = run(*run_argv)
File "/Library/
return self.run(
File "/Library/
revisions = branch.
File "/Library/
return unbound(self, *args, **kwargs)
File "/Library/
return self._get_
File "/Library/
return unbound(self, *args, **kwargs)
File "/Library/
self.
File "/Library/
texts = self._get_
File "/Library/
raise errors.
NoSuchRevision: KnitRevisionSto
bzr 0.93.0.dev.0 on python 2.5.1.final.0 (darwin)
arguments: ['/usr/
encoding: 'UTF-8', fsenc: 'utf-8', lang: 'hu_HU.UTF-8'
plugins:
launchpad /Library/
multiparent /Library/
qbzr /Library/
** Please send this report to <email address hidden>
with a description of what you were doing when the
error occurred.
---
Running 'bzr annotate NEWS' in the same directory gives the expected output without any problems.
I've tried a bunch of other files. Some of them did work, some others did not. (Failed the same way as above.)
If you need more info, don't hesitate to reply, I'll try to debug the problem if you help me. (The computer is running Mac OS X 10.5, with built-in Python 2.5.1)
Related branches
Changed in qbzr: | |
milestone: | none → 0.7.1 |
Changed in qbzr: | |
assignee: | nobody → bialix |
status: | Confirmed → In Progress |
Changed in qbzr: | |
status: | Fix Committed → Fix Released |
It's strange, because I can't reproduce it on win32 now. Can you say what revno of bzr.dev you're using?
I found qannotate is slightly suboptimal, because it try to collect info about each revisions that touch annotated file, not only revisions that touch annotated file last.
I think I ran into this too, probably because in shared repo there is branches that touch the file later. I'm not sure.
Not sure how to reproduce it. Can you run qannotate in stand-alone branch, not in branch that resides in shared repo?