Re: Issue 3191 in reviewboard: consequent searches crash with 'initVM() must be called first' error

Comment #3 on issue 3191 by bod...@gmail.com: consequent searches crash with 'initVM() must be called first' error http://code.google.com/p/reviewboard/issues/detail?id=3191 Thanks for comments guys. Do you have any estimates, when the 2.0 final release will be available? Thanks, Bogdan

Re: Issue 3191 in reviewboard: consequent searches crash with 'initVM() must be called first' error

Comment #4 on issue 3191 by chip...@gmail.com: consequent searches crash with 'initVM() must be called first' error http://code.google.com/p/reviewboard/issues/detail?id=3191 It's going to depend on beta 2 feedback. We should be releasing beta 2 today, so you can give that a try when it's

Re: Issue 3191 in reviewboard: consequent searches crash with 'initVM() must be called first' error

Updates: Status: Confirmed Comment #1 on issue 3191 by chip...@gmail.com: consequent searches crash with 'initVM() must be called first' error http://code.google.com/p/reviewboard/issues/detail?id=3191 PyLucene changes their API basically all the time. You need to have a pretty

Re: Issue 3191 in reviewboard: consequent searches crash with 'initVM() must be called first' error

Updates: Status: WontFix Comment #2 on issue 3191 by trowb...@gmail.com: consequent searches crash with 'initVM() must be called first' error http://code.google.com/p/reviewboard/issues/detail?id=3191 In fact, given that we're replacing the backend entirely, and pylucene bugs are