Commit command never completes and consumes 100% CPU

[Nicholas Allen]

I think what happened is I started indexing that branch and then
cancelled it because it took so long. Then when I next committed in that
branch it tried to resume indexing where it left off. I'm not sure how
best to fix that from a UI point of view. I think bzr-search should be
clearer that it's updating the search index. I noticed the "Indexing
texts" message in the progress bar but assumed this was something Bazaar
needed to do in order to commit. If the status bar said "Updating search
index" instead it would have been immediately clear to me. But I still
think aborting the index update should not abort the commit on the local
side (the remote side committed fine though).

Nick

John Arbash Meinel wrote:
> Nicholas Allen wrote:
> > Looking at the stack trace it seems to be the search plugin that is
> > causing this. After unistalling the plugin this problem went away. I'll
> > report a bug in bzr-search plugin....
>
> > Nick
>
>
> Yeah, I would guess there is a config possibility with bzr-search, to
> tell it whether or not you want a branch indexed.
>
> My guess is that the branch *wasn't* indexed, then you installed
> bzr-search, and now it is trying to index every branch that wasn't
> indexed before.
>
> I would guess that creating the index this time will be slow, but any
> future updates will be fast.
>
> Also, potentially you have the index already generated in the branch you
> did your other work on, and there may be a way to bring that index
> across, rather than regenerating it from scratch.
>
> John
> =:->
>