"too many SQL variables" when doing rebuild_index on sqlite3 backend
Hi. So, search broke some while ago and I'm trying to make it work again. I'm trying to rebuild the search index from scratch following the instructions from https://www.reviewboard.org/docs/manual/2.0/admin/sites/search-indexing/ but I get the following: # "/usr/local/bin/rb-site" manage "/var/www/reviews" rebuild_index WARNING: This will irreparably remove EVERYTHING from your search index in connection 'default'. Your choices after this are to restore from backups or rebuild via the `rebuild_index` command. Are you sure you wish to continue? [y/N] y Removing all documents from your index because you said so. All documents removed. Indexing 16022 review requests ERROR:root:Error updating reviews using default Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/django_haystack-2.2.1-py2.7.egg/haystack/management/commands/update_index.py", line 221, in handle_label self.update_backend(label, using) File "/usr/local/lib/python2.7/dist-packages/django_haystack-2.2.1-py2.7.egg/haystack/management/commands/update_index.py", line 266, in update_backend do_update(backend, index, qs, start, end, total, self.verbosity) File "/usr/local/lib/python2.7/dist-packages/django_haystack-2.2.1-py2.7.egg/haystack/management/commands/update_index.py", line 89, in do_update backend.update(index, current_qs) File "/usr/local/lib/python2.7/dist-packages/django_haystack-2.2.1-py2.7.egg/haystack/backends/whoosh_backend.py", line 188, in update for obj in iterable: File "/usr/local/lib/python2.7/dist-packages/Django-1.6.7-py2.7.egg/django/db/models/query.py", line 96, in __iter__ self._fetch_all() [...] File "/usr/local/lib/python2.7/dist-packages/Django-1.6.7-py2.7.egg/django/db/backends/sqlite3/base.py", line 452, in execute return Database.Cursor.execute(self, query, params) OperationalError: too many SQL variables Traceback (most recent call last): File "/usr/local/bin/rb-site", line 9, in load_entry_point('ReviewBoard==2.0.7', 'console_scripts', 'rb-site')() File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.7-py2.7.egg/reviewboard/cmdline/rbsite.py", line 1858, in main command.run() File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.7-py2.7.egg/reviewboard/cmdline/rbsite.py", line 1787, in run site.run_manage_command(args[0], args[1:]) File "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.7-py2.7.egg/reviewboard/cmdline/rbsite.py", line 645, in run_manage_command execute_from_command_line([__file__, cmd] + params) File "/usr/local/lib/python2.7/dist-packages/Django-1.6.7-py2.7.egg/django/core/management/__init__.py", line 399, in execute_from_command_line utility.execute() File "/usr/local/lib/python2.7/dist-packages/Django-1.6.7-py2.7.egg/django/core/management/__init__.py", line 392, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/local/lib/python2.7/dist-packages/Django-1.6.7-py2.7.egg/django/core/management/base.py", line 242, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/local/lib/python2.7/dist-packages/Django-1.6.7-py2.7.egg/django/core/management/base.py", line 285, in execute output = self.handle(*args, **options) [...] File "/usr/local/lib/python2.7/dist-packages/Django-1.6.7-py2.7.egg/django/db/backends/util.py", line 53, in execute return self.cursor.execute(sql, params) File "/usr/local/lib/python2.7/dist-packages/Django-1.6.7-py2.7.egg/django/db/backends/sqlite3/base.py", line 452, in execute return Database.Cursor.execute(self, query, params) django.db.utils.OperationalError: too many SQL variables I'm using sqlite3 as backend. It seems that sqlite3 is limited to SQLITE_MAX_VARIABLE_NUMBER, which defaults to 999, as found on http://stackoverflow.com/questions/7106016/too-many-sql-variables-error-in-django-witih-sqlite3. Any way to bypass this limitation and bring back the search? Thanks, Adrian -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Cannot change general option: server url
I use the current (2 days old) bitnami stack for reviewboard. Desparately trying to get rbtools running I found that a setting was missing in reviewboard. In System Settings -> General -> General Settings -> Site Settings There is the server URL. Now I use two Apaches one in the bitnami stack and one as a reverse proxy in front. I also changed the http port of the bitnami-Apache, as I got multiple bitnami stacks on my tools-server. So requests to the reviewboard arrive as: http://localhost:6080/... So in the menu the server URL is: http://localhost:6080 Reviewboard is quite picky about what it accepts as a server URL. When I try to change it, a moment later reviewboard resets it to localhost. What a litlle . *"§$% ! Any clue? -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Stuck with setup of rbtools
In a previous request for help, I learned that I was simply trying to use a feature that is not there for gitlab-repos, yet. Understood! I got hinted to use the rbtools. I followed that advice, and for test-purposes installed the rbtools, following the documentation. rbt can be started, now. Now I am stuck with adding the repository. While the documentation is surely well meant and understandable for someone having a bit experience in this special area, it leaves a lot open for me, despite being a seasoned developer. Probably I am getting old. Facts: - Centos actual - rbt 0.6.1 Trying "rbt setup-repo" asks for the RB server URL. Assuming myserver is myserver.net: http://myserver.net/reviewboard/ (I tried with and without trailing slash, my server uses an Apache reverse proxy in front of the actual bitnami stack for reviewboard, so the trailing slash would be required.) No Git repository found or selected for http://wallaschek.net/reviewboard/. .reviewboardrc not created. This error message gives me ... no clue where to search further. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Cannot access gitlab repository
Hi! First: regarding reviewboard I am a newB! I did setup the bitname-stack for RB ... that worked nicely. I did configure my gitlab repository and with some latency and experimentation, it showed up in the admin dashboard with no errors. (First it did configure, but did not show up, maybe a caching problem, dunno.) Now I have configured a repository with one initial checking available, but I cannot do a post-checkin review as the checkin is not shown when I try to create a review request for this repo. It only offers to upload a diff, but there is no history below as described in the docs. I run RB 2.0.2, latest bitnami stack. Is there anything newB-style that I might have misunderstood, mistaken, messed-up? Thanks in advance for any hint! -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Review Board on Heroku?
Hello -- Has anyone successfully ran Review Board on top of Heroku? Before I go down this route, I'd like to know any roadblocks that may have been hit. Cheers, //adrian -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
exporting all of a group's reviews
Hi -- First, my apologies if this is addressed somewhere -- I looked and couldn't find any information. I am currently working for a company that uses ReviewBoard. My group is being divested. We'd like to take our reviews with us. Is there a way to export all of the reviews from a specific group and import them into a separate ReviewBoard server? The current proposal is to clone the existing server and manually sanitize it by deleting groups/reviews/users from the administrative interface. I'm hoping that there is a better way! Thanks, //adrian -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: gitolite and ReviewBoard
I have no doubt that the ".reviweboardrc" mechanism will make post- review work... but it's still a work-around to the actual problem. It is kind of cumbersome to have to rely on NFS plus the .reviewboardrc. We would rather connect directly via ssh:// but we can't get this to work properly. //adrian On Nov 7, 2:59 pm, Christian Hammond wrote: > Hi Adrian, > > post-review will try to compare the repository paths by default. However, > you can tell it explicitly which repository to use by specifying REPOSITORY > = '' in a .reviewboardrc file committed in the base of the repository. > > This goes into some detail: > > http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/#r... > > So long as the repositories referenced are identical, you should be good. > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board -http://www.reviewboard.org > VMware, Inc. -http://www.vmware.com > > > > > > > > On Fri, Nov 4, 2011 at 6:25 PM, adrian wrote: > > Hello again -- > > > We just tried using the NFS method suggested by Maciek. While > > ReviewBoard is happy with this configuration, it breaks "post- > > review". The post-review tool uses origin.url and ReviewBoard > > complains that this repository does not exist. Because of this, it's > > not really a workable solution. Any other ideas? > > > //adrian > > > On Nov 4, 12:29 pm, adrian wrote: > > > On Nov 4, 11:16 am, Christian Hammond wrote: > > > > > SSH is supposed to work. We use it (for repo verification, though you > > still > > > > need the cgit, etc. method for getting files). > > > > > You'd need to go into RB and generate a new SSH key and then configure > > it > > > > for access on the git server. Should in theory work then. > > > > Hi Christian et al -- thanks for the responses. > > > > Note that this isn't an issue with the SSH keys -- that part works > > > fine. We've tried both using pre-existing keys and letting > > > ReviewBoard create its own. Both work. The issue is when the "git ls- > > > remote" command is issued. > > > > path = "ssh://...@mydomain.com/gitolite.git" => "A repository was not > > > found at the specified path." > > > path = "ssh://...@mydomain.com:gitolite.git" => "(-2, 'Name or > > > service not known')" > > > -- > > Want to help the Review Board project? Donate today at > >http://www.reviewboard.org/donate/ > > Happy user? Let us know athttp://www.reviewboard.org/users/ > > -~--~~~~--~~--~--~--- > > To unsubscribe from this group, send email to > > reviewboard+unsubscr...@googlegroups.com > > For more options, visit this group at > >http://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: gitolite and ReviewBoard
Hello again -- We just tried using the NFS method suggested by Maciek. While ReviewBoard is happy with this configuration, it breaks "post- review". The post-review tool uses origin.url and ReviewBoard complains that this repository does not exist. Because of this, it's not really a workable solution. Any other ideas? //adrian On Nov 4, 12:29 pm, adrian wrote: > On Nov 4, 11:16 am, Christian Hammond wrote: > > > SSH is supposed to work. We use it (for repo verification, though you still > > need the cgit, etc. method for getting files). > > > You'd need to go into RB and generate a new SSH key and then configure it > > for access on the git server. Should in theory work then. > > Hi Christian et al -- thanks for the responses. > > Note that this isn't an issue with the SSH keys -- that part works > fine. We've tried both using pre-existing keys and letting > ReviewBoard create its own. Both work. The issue is when the "git ls- > remote" command is issued. > > path = "ssh://...@mydomain.com/gitolite.git" => "A repository was not > found at the specified path." > path = "ssh://...@mydomain.com:gitolite.git" => "(-2, 'Name or > service not known')" -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: gitolite and ReviewBoard
On Nov 4, 11:16 am, Christian Hammond wrote: > SSH is supposed to work. We use it (for repo verification, though you still > need the cgit, etc. method for getting files). > > You'd need to go into RB and generate a new SSH key and then configure it > for access on the git server. Should in theory work then. Hi Christian et al -- thanks for the responses. Note that this isn't an issue with the SSH keys -- that part works fine. We've tried both using pre-existing keys and letting ReviewBoard create its own. Both work. The issue is when the "git ls- remote" command is issued. path = "ssh://g...@mydomain.com/gitolite.git" => "A repository was not found at the specified path." path = "ssh://g...@mydomain.com:gitolite.git" => "(-2, 'Name or service not known')" -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
gitolite and ReviewBoard
Hello -- We're having a hard time configuring ReviewBoard for use with Git repositories managed by gitlolite. One of the issues we see is that ReviewBoard executes a command like: > $ git ls-remote g...@git.mydomain.com/gitolite HEAD > fatal: 'g...@git.mydomain.com/gitolite' does not appear to be a git repository > fatal: The remote end hung up unexpectedly It seems that it should be doing this instead: > $ git ls-remote g...@git.mydomain.com:gitolite.git HEAD > bfb7d1766371452f117a96ccd689892855107cae HEAD Is this a supported configuration in gitolite? Is there something that we've set up incorrectly? When adding a repository, we've tried the following: > path: ssh://g...@git.mydomain.com/gitolite.git > path: ssh://g...@git.mydomain.com:gitolite.git > path: g...@git.mydomain.com/gitolite.git > path: g...@git.mydomain.com:gitolite.git None of these seem to work. Any help is appreciated. //adrian -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en