KeyError in _terms_for_file_terms lambda indexing 2a copy of Loggerhead
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bzr search plugin |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Revision 370 of lp:loggerhead makes "bzr index" die with a KeyError when using a 2a repo. The previous revision is fine. It's fine in my old 1.9-rich-root repo, too.
That revision does some kinda complicated renaming, so it could be confusing things (in bzr-search or maybe even bzr):
$ bzr st -c 370 --short
+N serve-branches
M loggerhead/
RM* serve-branches => loggerhead/main.py
M loggerhead/
Hmm, the particular revision referenced in the KeyError (r261) is just a YUI upgrade, creating and modifying a bunch of files but not actually anything related to revision 370.
(My 2a copy of Loggerhead is at lp:~mnordhoff/+junk/trunk.2a, or http://
bzr.dev r4475, bzr-search r71.
| Matt Nordhoff (mnordhoff) wrote | #1 |
| Matt Nordhoff (mnordhoff) wrote | #2 |
| Robert Collins (lifeless) wrote | #3 |
| Changed in bzr-search: | |
| status: | New → Incomplete |
| Matt Nordhoff (mnordhoff) wrote | #4 |
| Changed in bzr-search: | |
| status: | Incomplete → Invalid |
| Robert Collins (lifeless) wrote | #5 |
FWIW: Yesterday, it started complaining about a different revision, <email address hidden>. Today, it works perfectly.