Strange behaviour after updating to 1.6
Hello, I decided to update from 1.5.4 to 1.6. While the update procedure seems to have ran fine [1], my rb site stopped working correctly. First, I was getting this error [2] whenever I tried to add a comment to a review request. Then, after cleaning the browser's cache, I started receiving JS errors on a review page [3] and the page just doesn't behave properly -- e.g. the Close/Add screenshot/Update diff/... menu is broken (displayed as a list), and when switching to View diff I can't click anywhere on the code. Additionally, the header of the page still says Review Board 1.5.4. Anybody knows how I can fix this? Thank you, Olek Piekarz [1] user@server:/var/www/codereview$ sudo rb-site upgrade /var/www/ codereview/ Rebuilding directory structure Upgrading site settings_local.py Updating database. This may take a while. /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/ __init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated; use settings.DATABASES instead. DeprecationWarning /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/ __init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.' DeprecationWarning Creating tables ... Creating table accounts_localsiteprofile Creating table attachments_fileattachment Creating table reviews_fileattachmentcomment Creating table site_localsite_users Creating table site_localsite_admins Creating table site_localsite Upgrading Review Board from 1.5.4 to 1.6 There are unapplied evolutions for sessions. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Adding baseline version for new models Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... No fixtures found. Registering new SCM Tool Plastic SCM (reviewboard.scmtools.plastic.PlasticTool) in database Evolution could not be simulated, possibly due to raw SQL mutations Evolution successful. Resetting in-database caches. Upgrade complete. [2] Error Code: 500 Error Text: Internal Server Error Request URL: /api/json/reviewrequests/353/diff/1/file/23964/line/21/ comments/ Request Data: action=setnum_lines=1text=Isn't+the+main+properties +file+already+loaded+in+the+build.hudson.xml+available+to+the+child +build.xml+through+the+use+of+the++inheritall+attribute%3F+Because+then %2C+this+property+wouldn't+be+needed. Response Data: There may be useful error details below. The following error page may be useful to your system administrator or when reporting a bug. To save the page, right-click the error below and choose Save Page As, if available, or View Source and save the result as a .html file. Warning: Be sure to remove any sensitive material that may exist in the error page before reporting a bug! Warning at /api/json/reviewrequests/353/diff/1/file/23964/line/21/ comments/ Field 'issue_opened' doesn't have a default value Request Method: POST Request URL: http://codereview/api/json/reviewrequests/353/diff/1/file/23964/line/21/comments/ Django Version: 1.2.5 Exception Type: Warning Exception Value: Field 'issue_opened' doesn't have a default value Exception Location: /usr/lib/python2.5/warnings.py in warn_explicit, line 102 Python Executable: /var/lib/django/environments/reviewboard/bin/ python Python Version: 2.5.2 Python Path: ['/var/lib/django', '/opt/reviewboard/lib/python2.5/ site-packages/ReviewBoard-1.5.4-py2.5.egg/reviewboard', '/var/lib/ django/environments/reviewboard/lib/python2.5/site-packages/ setuptools-0.6c8-py2.5.egg', '/var/lib/django/environments/reviewboard/ lib/python2.5/site-packages/ReviewBoard-1.5.4-py2.5.egg', '/var/lib/ django/environments/reviewboard/lib/python2.5/site-packages/ recaptcha_client-1.0.5-py2.5.egg', '/var/lib/django/environments/ reviewboard/lib/python2.5/site-packages/python_memcached-1.47- py2.5.egg', '/var/lib/django/environments/reviewboard/lib/python2.5/ site-packages/python_dateutil-1.5-py2.5.egg', '/var/lib/django/ environments/reviewboard/lib/python2.5/site-packages/paramiko-1.7.6- py2.5.egg', '/var/lib/django/environments/reviewboard/lib/python2.5/ site-packages/Pygments-1.4-py2.5.egg', '/var/lib/django/environments/ reviewboard/lib/python2.5/site-packages/Djblets-0.6.7-py2.5.egg', '/ var/lib/django/environments/reviewboard/lib/python2.5/site-packages/ django_evolution-0.6.2-py2.5.egg', '/var/lib/django/environments/ reviewboard/lib/python2.5/site-packages/Django-1.2.5-py2.5.egg', '/var/ lib/django/environments/reviewboard/lib/python2.5/site-packages/ pycrypto-2.3-py2.5-linux-x86_64.egg', '/var/lib/django/environments/ reviewboard/lib/python2.5/site-packages/PIL-1.1.6-py2.5-linux- x86_64.egg', '/var/lib/django/environments/reviewboard/lib/python2.5/ site-packages/RBTools-0.3.2-py2.5.egg',
Re: Strange behaviour after updating to 1.6
Hi Olek, That backtrace shows that you're still running Review Board 1.5.4. Did you restart your web server? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Sep 7, 2011 at 2:15 AM, Olek Piekarz aleksander.piek...@gmail.comwrote: Hello, I decided to update from 1.5.4 to 1.6. While the update procedure seems to have ran fine [1], my rb site stopped working correctly. First, I was getting this error [2] whenever I tried to add a comment to a review request. Then, after cleaning the browser's cache, I started receiving JS errors on a review page [3] and the page just doesn't behave properly -- e.g. the Close/Add screenshot/Update diff/... menu is broken (displayed as a list), and when switching to View diff I can't click anywhere on the code. Additionally, the header of the page still says Review Board 1.5.4. Anybody knows how I can fix this? Thank you, Olek Piekarz [1] user@server:/var/www/codereview$ sudo rb-site upgrade /var/www/ codereview/ Rebuilding directory structure Upgrading site settings_local.py Updating database. This may take a while. /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/ __init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated; use settings.DATABASES instead. DeprecationWarning /usr/lib/python2.5/site-packages/Django-1.3-py2.5.egg/django/db/ __init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.' DeprecationWarning Creating tables ... Creating table accounts_localsiteprofile Creating table attachments_fileattachment Creating table reviews_fileattachmentcomment Creating table site_localsite_users Creating table site_localsite_admins Creating table site_localsite Upgrading Review Board from 1.5.4 to 1.6 There are unapplied evolutions for sessions. There are unapplied evolutions for accounts. There are unapplied evolutions for changedescs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. Adding baseline version for new models Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... No fixtures found. Registering new SCM Tool Plastic SCM (reviewboard.scmtools.plastic.PlasticTool) in database Evolution could not be simulated, possibly due to raw SQL mutations Evolution successful. Resetting in-database caches. Upgrade complete. [2] Error Code: 500 Error Text: Internal Server Error Request URL: /api/json/reviewrequests/353/diff/1/file/23964/line/21/ comments/ Request Data: action=setnum_lines=1text=Isn't+the+main+properties +file+already+loaded+in+the+build.hudson.xml+available+to+the+child +build.xml+through+the+use+of+the++inheritall+attribute%3F+Because+then %2C+this+property+wouldn't+be+needed. Response Data: There may be useful error details below. The following error page may be useful to your system administrator or when reporting a bug. To save the page, right-click the error below and choose Save Page As, if available, or View Source and save the result as a .html file. Warning: Be sure to remove any sensitive material that may exist in the error page before reporting a bug! Warning at /api/json/reviewrequests/353/diff/1/file/23964/line/21/ comments/ Field 'issue_opened' doesn't have a default value Request Method: POST Request URL: http://codereview/api/json/reviewrequests/353/diff/1/file/23964/line/21/comments/ Django Version: 1.2.5 Exception Type: Warning Exception Value: Field 'issue_opened' doesn't have a default value Exception Location: /usr/lib/python2.5/warnings.py in warn_explicit, line 102 Python Executable: /var/lib/django/environments/reviewboard/bin/ python Python Version: 2.5.2 Python Path: ['/var/lib/django', '/opt/reviewboard/lib/python2.5/ site-packages/ReviewBoard-1.5.4-py2.5.egg/reviewboard', '/var/lib/ django/environments/reviewboard/lib/python2.5/site-packages/ setuptools-0.6c8-py2.5.egg', '/var/lib/django/environments/reviewboard/ lib/python2.5/site-packages/ReviewBoard-1.5.4-py2.5.egg', '/var/lib/ django/environments/reviewboard/lib/python2.5/site-packages/ recaptcha_client-1.0.5-py2.5.egg', '/var/lib/django/environments/ reviewboard/lib/python2.5/site-packages/python_memcached-1.47- py2.5.egg', '/var/lib/django/environments/reviewboard/lib/python2.5/ site-packages/python_dateutil-1.5-py2.5.egg', '/var/lib/django/ environments/reviewboard/lib/python2.5/site-packages/paramiko-1.7.6- py2.5.egg', '/var/lib/django/environments/reviewboard/lib/python2.5/ site-packages/Pygments-1.4-py2.5.egg', '/var/lib/django/environments/ reviewboard/lib/python2.5/site-packages/Djblets-0.6.7-py2.5.egg', '/ var/lib/django/environments/reviewboard/lib/python2.5/site-packages/ django_evolution-0.6.2-py2.5.egg',
Re: Strange behaviour after updating to 1.6
Hi, Thank you for the fast reply. Yes, I restarted it, more than once actually. I also flushed memcache. Olek -- 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: Strange behaviour after updating to 1.6
Okay, the problem appears to be this: You installed Review Board (and Django and all other accompanying dependencies) in /usr/lib/python2.5/..., as is the default for easy_install. However, your Apache is running off of a different Review Board/Python install in /opt/reviewboard/lib/python2.5/... You'll need to nuke the old install, do another rb-site upgrade just to be safe, possibly edit your Apache configuration to not point to the old install, and restart Apache again. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Sep 7, 2011 at 2:37 AM, Olek Piekarz aleksander.piek...@gmail.comwrote: Hi, Thank you for the fast reply. Yes, I restarted it, more than once actually. I also flushed memcache. Olek -- 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 -- 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
Queries:Postreview.py [Perforce]
Hi, 1. Does post-review tools has any restriction to upload some restricted number of files to reviewboard, if changelist contain more then 1000 files will it effect the performance of Reviewbaord. 2. It might possible that user had send code for review and after changes are approve he may modify the changes or add add some more files in the change list and submit to perforce.Do we perform some sort of checksum eg md5 on diff files so that before submitting the files to perforce server, changes are verified and check if there are some extra changes made by the user. Thanks, Nilesh -- 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
RBTools: wrong repository path
Hi folks, I don't understand how post-review extracts the path of the repository. Ex: $ ./bin/post-review ... The repository path ssh://server/srv/git/vendor/rbtools.git is not in the list of known repositories on the server. Right, the repository is path + repo_name (/srv/git/vendor/rbtools.git) and not server_url + path + repo_name. Did I missed something? PS: I use server alias: [url ssh://server/srv/git] insteadOf = sact: So, automatic url / path extraction doesn't work. A better way could be to add a reviewboard configuration in gitconfig the like this: [reviewboard] path = /srv/git/repo_name.git I've a patch for that. -- Sebastien Douche sdou...@gmail.com Twitter : @sdouche -- 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: Failure upgrading to 1.6
I would recommend to do a check by the software to verify permissions on DB before performing the upgrade, if the requirements are missing it can inform the user to get the requirements done before it performs the upgrade. Also, It can avoid database getting into a fuzzy state (neither downgraded nor upgraded) during the upgrade. Thanks, Kannaiyan On Tue, Sep 6, 2011 at 12:19 PM, Christian Hammond chip...@chipx86.comwrote: On Tue, Sep 6, 2011 at 10:08 AM, Kannaiyan Natesan gbpnk...@gmail.comwrote: INDEX command denied to user 'rb'@'localhost' for table 'accounts_localsiteprofile') Seems a Database Issue. Did you verify permissions for this user on Database? Kannaiyan Right, it looks like the user just doesn't have all the necessary permissions. Quickest thing to do is: GRANT ALL ON yourdbname.* to rb@localhost; You could instead do INDEX instead of ALL, I think, but might be safest to just give the user the permissions it needs to manipulate that database. Your database isn't corrupt, but you're probably not at a spot now where you'd be able to downgrade. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- 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 -- 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 -- The best things in life are free -- 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
Problem with WSGI on fresh install
Hello everybody. I install a new Review Board 1.6 on one of my server, but I have a problem after setup. I install RB on an already existing Apache virtualhost and merge manually RB conf with existing one. After restarting Apache, if I access to http://myHost/reviews/, I get a 404 RB error : The page you were looking for does not exist. If you're pretty sure this page does exist, try logging in and trying again. If I click the login link (http://myHost/reviews/account/login/), I get a 404 Apache error : Not Found The requested URL /reviews/account/login/ was not found on this server. On Apache log, I have this error : Target WSGI script not found or unable to stat: /opt/reviewboard/htdocs/reviewboard.wsgiaccount, referer: http://myHost/reviews/ Here is enclosed my Apache conf. Where I'm wrong ? Thanks in advance -- 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 apache.conf Description: Binary data
Problem with WSGI on fresh install
Hello everybody.
I install a new Review Board 1.6 on one of my server, but I have a problem
after setup.
I install RB on an already existing Apache virtualhost and merge manually RB
conf with existing one.
After restarting Apache, if I access to http://myHost/reviews/, I get a 404 RB
error :
The page you were looking for does not exist.
If you're pretty sure this page does exist, try logging in and trying
again.
If I click the login link (http://myHost/reviews/account/login/), I get a 404
Apache error :
Not Found
The requested URL /reviews/account/login/ was not found on this server.
On Apache log, I have this error :
Target WSGI script not found or unable to stat:
/opt/reviewboard/htdocs/reviewboard.wsgiaccount, referer:
http://myHost/reviews/
Here is enclosed my Apache conf.
Where I'm wrong ?
Thanks in advance
--
Nicolas VINOT
VirtualHost *:80
ServerName myHost.myDomain
ServerAlias myHost
DocumentRoot /var/www/myDomain/myHost
ErrorLog ${APACHE_LOG_DIR}/myDomain-error.log
CustomLog ${APACHE_LOG_DIR}/myDomain.log combined
# Other not reviewboard configuration
…
# Other not reviewboard configuration
WSGIPassAuthorization On
WSGIScriptAlias /reviews/ /opt/reviewboard/htdocs/reviewboard.wsgi
Directory /opt/reviewboard/htdocs
AllowOverride All
Options +FollowSymLinks
/Directory
Location /reviews/
ErrorDocument 500 /errordocs/500.html
/Location
# Alias static media requests to filesystem
Alias /reviews/media /opt/reviewboard/htdocs/media
Alias /reviews/errordocs /opt/reviewboard/htdocs/errordocs
Alias /reviews/favicon.ico
/opt/reviewboard/htdocs/media/rbcommons/images/favicon.png
/VirtualHost
signature.asc
Description: This is a digitally signed message part.
Fedora 2.6 Installation
I followed the instructions to install ReviewBoard on Linux but I cannot get it to work. I create a linux server where I installed all the requisites. I'm working in the apache configuration right now and I cannot make it to work. This is a test server. My apache server runs as root. I defined that I wanted to use fastcgi. I modified the httpd.conf file and I added at the end of the file the file generated from reviewboard called apache-fastcgi.conf. I create the test site reviews.example.com (as per the documentation) I restart apache and I got error 404 The logs file show the problem was that the file reviews.example.com/ htdocs/reviewboard.fcgi was suppose to be a directory not a folder. I create it as a folder and put the file with the same name below it. When I try http://localhost I'm getting: Forbidden You don't have permission to access / on the server Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. - Apache 2.2.9 (Fedora) Server at localhost Port 80 When I try http://localhost/reviewboard I'm getting the contents of the file reviewboard.fcgi like text: #!/usr/bin/env python import os, sys sys.path.insert(0, /software/tools/reviewBoard/sites/ reviews.example.com/conf) os.environ[DJANGO_SETTINGS_MODULE] = reviewboard.settings os.environ[PYTHON_EGG_CACHE] = /software/tools/reviewBoard/ sites/reviews.example.com /tmp/egg_cache os.environ[HOME] = /software/tools/reviewBoard/sites/ reviews.example.com/data from django.core.servers.fastcgi import runfastcgi runfastcgi(method=threaded, daemonize=false) What am I doing wrong? Please help. Thank you -- 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: Strange behaviour after updating to 1.6
I finally have it up and running, after preparing pretty much a fresh install. Thank you very much Christian! Cheers, Olek -- 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: RBTools: wrong repository path
Hi Sebastien, The best thing to do is to move to named repositories, by creating a .reviewboardrc and doing: REPOSITORY = my repo name Where my repo name is the exact name for the repository entry in Review Board. That way, it won't have to do path comparisons. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Sep 7, 2011 at 5:02 AM, Sebastien Douche sdou...@gmail.com wrote: Hi folks, I don't understand how post-review extracts the path of the repository. Ex: $ ./bin/post-review ... The repository path ssh://server/srv/git/vendor/rbtools.git is not in the list of known repositories on the server. Right, the repository is path + repo_name (/srv/git/vendor/rbtools.git) and not server_url + path + repo_name. Did I missed something? PS: I use server alias: [url ssh://server/srv/git] insteadOf = sact: So, automatic url / path extraction doesn't work. A better way could be to add a reviewboard configuration in gitconfig the like this: [reviewboard] path = /srv/git/repo_name.git I've a patch for that. -- Sebastien Douche sdou...@gmail.com Twitter : @sdouche -- 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 -- 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: Fedora 2.6 Installation
Hi, Can you show the resulting Apache configuration? Also, is fastcgi installed on your system? (We heavily recommend wsgi, btw, as we've seen issues in the past with fastcgi in general.) Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Sep 7, 2011 at 10:00 AM, MonicaS castaneda.mon...@gmail.com wrote: I followed the instructions to install ReviewBoard on Linux but I cannot get it to work. I create a linux server where I installed all the requisites. I'm working in the apache configuration right now and I cannot make it to work. This is a test server. My apache server runs as root. I defined that I wanted to use fastcgi. I modified the httpd.conf file and I added at the end of the file the file generated from reviewboard called apache-fastcgi.conf. I create the test site reviews.example.com (as per the documentation) I restart apache and I got error 404 The logs file show the problem was that the file reviews.example.com/ htdocs/reviewboard.fcgihttp://reviews.example.com/%0Ahtdocs/reviewboard.fcgiwas suppose to be a directory not a folder. I create it as a folder and put the file with the same name below it. When I try http://localhost I'm getting: Forbidden You don't have permission to access / on the server Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. - Apache 2.2.9 (Fedora) Server at localhost Port 80 When I try http://localhost/reviewboard I'm getting the contents of the file reviewboard.fcgi like text: #!/usr/bin/env python import os, sys sys.path.insert(0, /software/tools/reviewBoard/sites/ reviews.example.com/conf) os.environ[DJANGO_SETTINGS_MODULE] = reviewboard.settings os.environ[PYTHON_EGG_CACHE] = /software/tools/reviewBoard/ sites/reviews.example.com /tmp/egg_cache os.environ[HOME] = /software/tools/reviewBoard/sites/ reviews.example.com/data from django.core.servers.fastcgi import runfastcgi runfastcgi(method=threaded, daemonize=false) What am I doing wrong? Please help. Thank you -- 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 -- 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: Queries:Postreview.py [Perforce]
On Wed, Sep 7, 2011 at 4:28 AM, NSJ nileshj...@gmail.com wrote: Hi, 1. Does post-review tools has any restriction to upload some restricted number of files to reviewboard, if changelist contain more then 1000 files will it effect the performance of Reviewbaord. We don't specifically restrict it, but it will put strain on the server. It's also just really hard for someone to review a change that size. It's best to break it up into manageable, logical chunks. 2. It might possible that user had send code for review and after changes are approve he may modify the changes or add add some more files in the change list and submit to perforce.Do we perform some sort of checksum eg md5 on diff files so that before submitting the files to perforce server, changes are verified and check if there are some extra changes made by the user. No, Review Board doesn't do any sort of pre-commit checks. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- 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: Failure upgrading to 1.6
Thanks for the help. I granted INDEX to user rb. I'm not sure why I would have granted USAGE, which is what it was. Anyhow, problem solved. Thanks again. On Sep 6, 2:19 pm, Christian Hammond chip...@chipx86.com wrote: On Tue, Sep 6, 2011 at 10:08 AM, Kannaiyan Natesan gbpnk...@gmail.comwrote: INDEX command denied to user 'rb'@'localhost' for table 'accounts_localsiteprofile') Seems a Database Issue. Did you verify permissions for this user on Database? Kannaiyan Right, it looks like the user just doesn't have all the necessary permissions. Quickest thing to do is: GRANT ALL ON yourdbname.* to rb@localhost; You could instead do INDEX instead of ALL, I think, but might be safest to just give the user the permissions it needs to manipulate that database. Your database isn't corrupt, but you're probably not at a spot now where you'd be able to downgrade. Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com -- Want to help the Review Board project? Donate today athttp://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 athttp://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 : Re: Problem with WSGI on fresh install
Thanks for your answer. Other stuff is just for Tomcat proxy Location / Order Deny,Allow Allow from 127.0.0.1 192.168.0.0/24 Deny from all /Location ProxyPreserveHost On ProxyPass/nexus ajp://localhost:8009/nexus ProxyPassReverse /nexus ajp://localhost:8009/nexus ProxyPass/jenkins ajp://localhost:8009/jenkins ProxyPassReverse /jenkins ajp://localhost:8009/jenkins ProxyPass/sonar ajp://localhost:8009/sonar ProxyPassReverse /sonar ajp://localhost:8009/sonar I don't think this stuff can involve on my RB problem. And yes, this is the only VirtualHost for this domain. For the file, /opt/reviewboard/htdocs/reviewboard.wsgiaccount doesn't exist, but /opt/reviewboard/htdocs/reviewboard.wsgi yes and it's executable. Seems Apache concatenate last part of the URL (account/login/ of http://myHost/reviews/account/login/ in my case) to WSGI executable (/opt/reviewboard/htdocs/reviewboard.wsgi). -- Nicolas VINOT -- 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: Fedora 2.6 Installation
On Wed, Sep 7, 2011 at 10:00 AM, MonicaS castaneda.mon...@gmail.com wrote: This is a test server. My apache server runs as root. httpd should run as user 'apache' on Fedora. The rpm installed with yum will install it that way, don't change it, and don't install apache httpd from source. I defined that I wanted to use fastcgi. Use WSGI. I modified the httpd.conf file and I added at the end of the file the file generated from reviewboard called apache-fastcgi.conf. The config file generated by rb-site should be put in /etc/httpd/conf.d/. You very rarely have to edit /etc/httpd/conf/httpd.conf, unless you really know what you are doing. What am I doing wrong? If this is testing for a real deployment, I would start over. Fedora is not a good server OS, it EOLs after 13 months and stops getting security updates. CentOS 6 is Red Hat-based and has a long life-cycle. Or use Ubuntu LTS or Debian stable. If you go with Red Hat-based, install everything from packages in yum repositories. With CentOS you can use the EPEL repository. An install on CentOS 6 would looks something like this, depending on the database and VCS you use: Install the packages: # sudo rpm -ivh http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-5.noarch.rpm # sudo yum groupinstall Web Server MySQL Database # sudo yum install ReviewBoard mod_wsgi memcached python-memcached git Configure and start memcached: # sudo vi /etc/sysconfig/memcached CACHESIZE=2048 # Or however much (in MB) RAM you want memcached to use. # sudo chkconfig memcached on # sudo service memcached start Start mysqld: # sudo chkconfig mysqld on # sudo service mysqld start Create an empty database: # mysql -u root CREATE DATABASE reviewboard; GRANT ALL PRIVILEGES ON reviewboard.* TO 'reviewboard'@'localhost' IDENTIFIED BY 'yourpassword'; Create site, it will create files and load the database: # sudo rb-site install /var/www/reviewboard Modify permission where apache has to write: # sudo chown -R apache:apache /var/www/reviewboard/htdocs/media/uploaded # sudo chown -R apache:apache /var/www/reviewboard/data Copy the apache config: # sudo cp /var/www/reviewboard/conf/apache-wsgi.conf /etc/httpd/conf.d/reviewboard.conf Start apache: # sudo chkconfig httpd on # sudo service httpd restart I'm probably missing something, but that's pretty close to a complete install. Hope that helps, Anton -- 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: Issue 1795 in reviewboard: using --submit-as with post-review causes generated mails to be from original submitter
Comment #3 on issue 1795 by michakel...@gmail.com: using --submit-as with post-review causes generated mails to be from original submitter http://code.google.com/p/reviewboard/issues/detail?id=1795 Is this a post-review issue? We run RB 1.5 beta 2, and see the same behavior. But the submitter in the review request is indeed the specified user (with correctly resolved e-mail address). But even later reviews to this request will never copy that submitter. Is it possible, that there is a general issue with the submitter of a review request being left out from notifications? -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2269 in reviewboard: reviewers can review uploaded file just like diff file
Comment #2 on issue 2269 by wangxiao...@gmail.com: reviewers can review uploaded file just like diff file http://code.google.com/p/reviewboard/issues/detail?id=2269 all files(.txt .java .c .h .php .js .css .xml .py .sh .pl etc) expect Binary files and pictures -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2272 in reviewboard: Automatic Update of Chagne Number in ReveiwBoard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2272 by jagtar.c...@gmail.com: Automatic Update of Chagne Number in ReveiwBoard http://code.google.com/p/reviewboard/issues/detail?id=2272 * NOTE: Do not post confidential information in this bug report. * * If you need immediate support, please contact* * reviewbo...@googlegroups.com * What version are you running? What's the URL of the page containing the problem? What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What operating system are you using? What browser? Please provide any additional information below. I am using ReviewBoard with Perforce. To create a Review, I need to make changes in Perforce and store that changes into 'Saved Numbered Changelist' say 1543. Now if the Review is reviewed next day, there might be more changes are submitted in the Perforce. When I am finally going to submit my change from ChangeList 1543, my changes are submitted with the lasted CL available say 1619. Now when I open the review anytime, the Change Number associated with that review display Change Number 1543. There is no reference of ChangeList 1619 in that particular review. Now my question is how to update the Change Number in ReviewBoard once I get approval of Ship It from the reviewer. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2272 in reviewboard: Automatic Update of Chagne Number in ReveiwBoard
Comment #1 on issue 2272 by chip...@gmail.com: Automatic Update of Chagne Number in ReveiwBoard http://code.google.com/p/reviewboard/issues/detail?id=2272 The change number can only be updated today through the API, as giving users the option to specify their own change number can actually cause problems due to how we treat the change number internally. Some places have a script that takes the new change number and uses the API to update it, but I don't have code you can use off-hand for this. If you're using Review Board 1.6, you can specify the change number the change was committed as in the Close Description message, which will provide the same effect. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 1795 in reviewboard: using --submit-as with post-review causes generated mails to be from original submitter
Updates: Labels: -Type-Defect Type-Enhancement Component-EMail Comment #4 on issue 1795 by chip...@gmail.com: using --submit-as with post-review causes generated mails to be from original submitter http://code.google.com/p/reviewboard/issues/detail?id=1795 It's part RBTools, part Review Board. But not really a bug, per se. --submit-as is used for the creation of a review request, to put it in someone else's name. That's a separate operation from publishing. When publishing, the e-mail will go out as the user logged in. There's definitely a use case for making a publish operations happen on behalf of another user, but we aren't set up for that today. So this would need to be added. One option is to just use the review request submitter for the e-mail, but that's likely not what we want in all cases. I'm hoping to introduce a multi-user workflow for review requests, where the ownership can be reassigned, and other users could modify fields with state being preserved to indicate who made the change. That won't solve your problem directly, though. You'd still need to either log in as the user, or would need to specifically do a --submit-as on that operation (which we'd have to support). -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2273 in reviewboard: number of incomming/outgoing reviews reset after migration to 1.6
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2273 by kofem...@googlemail.com: number of incomming/outgoing reviews reset after migration to 1.6 http://code.google.com/p/reviewboard/issues/detail?id=2273 * NOTE: Do not post confidential information in this bug report. * * If you need immediate support, please contact* * reviewbo...@googlegroups.com * What version are you running? 1.6 What's the URL of the page containing the problem? dashboard What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? What operating system are you using? What browser? Please provide any additional information below. after upgrade from 1.5.5 to 1.6 all counters was reset to zero. Now, after some patches get submitted counters start to decrease and become a negative numbers. I guess some DB schema change did not run completely. Attachments: Screenshot-My Dashboard | Review Board - Mozilla Firefox.png 7.9 KB -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2273 in reviewboard: number of incomming/outgoing reviews reset after migration to 1.6
Updates: Status: NeedInfo Labels: -Priority-Medium Priority-Critical Milestone-Release1.6.x Component-Dashboard Comment #1 on issue 2273 by chip...@gmail.com: number of incomming/outgoing reviews reset after migration to 1.6 http://code.google.com/p/reviewboard/issues/detail?id=2273 What type of database are you using? For now, try running: rb-site manage /path/to/site fixreviewcounts -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2273 in reviewboard: number of incomming/outgoing reviews reset after migration to 1.6
Comment #2 on issue 2273 by kofem...@googlemail.com: number of incomming/outgoing reviews reset after migration to 1.6 http://code.google.com/p/reviewboard/issues/detail?id=2273 I run Mysql 5.0.51a on debian lenny. fixreviewcounts did the job. Thanks. Attachments: Screenshot-My Dashboard | Review Board - Mozilla Firefox.png 8.1 KB -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2273 in reviewboard: number of incomming/outgoing reviews reset after migration to 1.6
Comment #3 on issue 2273 by chip...@gmail.com: number of incomming/outgoing reviews reset after migration to 1.6 http://code.google.com/p/reviewboard/issues/detail?id=2273 We thought we had this nailed down in the betas, but alas... We call fixreviewcounts on upgrade, which should have taken care of this. Strange that it did not, but someone else also reported this. We'll do more tests. It looks like the group counts were correct though? Given the difference in screenshots. So the broken fields were Starred, Outgoing, Incoming, To Me, and All My Requests? -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2273 in reviewboard: number of incomming/outgoing reviews reset after migration to 1.6
Comment #4 on issue 2273 by kofem...@googlemail.com: number of incomming/outgoing reviews reset after migration to 1.6 http://code.google.com/p/reviewboard/issues/detail?id=2273 It looks like the group counts were correct though? Given the difference in screenshots. So the broken fields were Starred, Outgoing, Incoming, To Me, and All My Requests? That's right, group counter where correct. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2268 in reviewboard: My incoming reviews have a negative number
Comment #6 on issue 2268 by manjunat...@gmail.com: My incoming reviews have a negative number http://code.google.com/p/reviewboard/issues/detail?id=2268 When I upgraded from 1.5 to 1.6, i got -1 for Outgoing Reviews and zero for all the other case (example Outgoing Reviews). When I ran rb-site manage path/to/site fixreviewcounts, counts were seen correctly (Outgoing Reviews now 83). -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2268 in reviewboard: My incoming reviews have a negative number
Comment #7 on issue 2268 by manjunat...@gmail.com: My incoming reviews have a negative number http://code.google.com/p/reviewboard/issues/detail?id=2268 When I upgraded from 1.5 to 1.6, i got -1 for Outgoing Reviews and zero for all the other case (example All My Requests). When I ran rb-site manage path/to/site fixreviewcounts, counts were seen correctly (All My Requests now 83). -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 1722 in reviewboard: UTF-16 file from Perforce not displayed
Comment #4 on issue 1722 by joshua.m...@gmail.com: UTF-16 file from Perforce not displayed http://code.google.com/p/reviewboard/issues/detail?id=1722 It just shows This is a binary file, contents cannot be displayed or whatever it usually does when encountering a binary file. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2268 in reviewboard: My incoming reviews have a negative number
Comment #8 on issue 2268 by trowb...@gmail.com: My incoming reviews have a negative number http://code.google.com/p/reviewboard/issues/detail?id=2268 Issue 2273 has been merged into this issue. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2274 in reviewboard: add Outgouing link to the dashboard
Updates: Status: WontFix Comment #1 on issue 2274 by chip...@gmail.com: add Outgouing link to the dashboard http://code.google.com/p/reviewboard/issues/detail?id=2274 Thanks, but this isn't how we'd like to tackle this. Rather, the idea is to have a drop-down arrow besides My Dashboard that will allow quick access to any dashboard page. It's a bit more work than adding a link, though. Might happen in 1.6.x. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2275 in reviewboard: Defect in the Bugs field
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2275 by gdinsh...@gmail.com: Defect in the Bugs field http://code.google.com/p/reviewboard/issues/detail?id=2275 * NOTE: Do not post confidential information in this bug report. * * If you need immediate support, please contact* * reviewbo...@googlegroups.com * What version are you running? 1.5.1 What's the URL of the page containing the problem? http://gpreview9300.houston.lgc.com/r/1151/ What steps will reproduce the problem? 1. In the bugs field I entered the following text: Defect Id 873851: Post Processing-Volumetrics; DSR and Java NPE when clicking next to Step 3 Calculate Fluid Saturation with Saturation-Height Model selected when using Grid only 2. After doing ok and publishing the defect the text somehow gets corrupted as you can see in the attachment. 3. What is the expected output? What do you see instead? The text should be as entered. I see instead a bunch of random comma separated words. What operating system are you using? What browser? Win 7 IE 8 Please provide any additional information below. Please fix this bug. Attachments: ReviewBoardBug-AFTER.png 158 KB ReviewBoardBug-BEFORE_PUBLISHING.png 172 KB -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2275 in reviewboard: Defect in the Bugs field
Updates: Status: UserError Comment #1 on issue 2275 by trowb...@gmail.com: Defect in the Bugs field http://code.google.com/p/reviewboard/issues/detail?id=2275 This is as expected. The bugs field is not supposed to be a text description, but rather a list of bug IDs to link. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2184 in reviewboard: Mercurial rename support: Pure file renames with *no actual changes* to the file fails with Diff did not apply cleanly
Comment #2 on issue 2184 by carl.van...@gmail.com: Mercurial rename support: Pure file renames with *no actual changes* to the file fails with Diff did not apply cleanly http://code.google.com/p/reviewboard/issues/detail?id=2184 This bug applies to more than just Mercurial changesets. I've tested in both mercurial and git that: (reviewboard 1.6RC2) 1. Renames without modifications 2. Deletes of empty files 3. Addition of empty files All three have similar properties in that the diff file contains meta data, but no actual diff headers, thus reviewboard internal patching fails. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
