EPEL - rb-site upgrade failure upon reboot prevents httpd startup
Hi all (and Stephen Gallagher), I'm using CentOS7 + EPEL with ReviewBoard-2.0.11 (fresh install + today's updates). My site is listed in /etc/reviewboard/sites. When httpd starts up, it checks if any sites need upgraded. I'm using a mariadb database. When I reboot the box, httpd fails to startup. $ sudo systemctl status httpd httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled) Drop-In: /usr/lib/systemd/system/httpd.service.d └─reviewboard-sites.conf Active: failed (Result: exit-code) since Wed 2014-10-29 17:42:28 GMT; 16s ago Process: 1184 ExecStartPre=/usr/bin/rb-site upgrade --all-sites (code=exited, status=1/FAILURE) Oct 29 17:42:28 centos7 rb-site[1184]: File /usr/lib/python2.7/site-packages/django/db/backends/mysql/base.py, line 435, in get_new_connection Oct 29 17:42:28 centos7 rb-site[1184]: conn = Database.connect(**conn_params) Oct 29 17:42:28 centos7 rb-site[1184]: File /usr/lib64/python2.7/site-packages/MySQLdb/__init__.py, line 81, in Connect Oct 29 17:42:28 centos7 rb-site[1184]: return Connection(*args, **kwargs) Oct 29 17:42:28 centos7 rb-site[1184]: File /usr/lib64/python2.7/site-packages/MySQLdb/connections.py, line 187, in __init__ Oct 29 17:42:28 centos7 rb-site[1184]: super(Connection, self).__init__(*args, **kwargs2) Oct 29 17:42:28 centos7 rb-site[1184]: django.db.utils.OperationalError: (2002, Can't connect to local MySQL server through socket '...k' (2)) Oct 29 17:42:28 centos7 systemd[1]: httpd.service: control process exited, code=exited status=1 Oct 29 17:42:28 centos7 systemd[1]: Failed to start The Apache HTTP Server. Oct 29 17:42:28 centos7 systemd[1]: Unit httpd.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. == I can manually start httpd as mariadb is now running by the time I've logged in. If I remove the /etc/reviewboard/sites file, the issue goes away. If I restore the file, the issue comes back. It looks like rb-site upgrade is being run before the database is available. Should systemd be using socket activation to start mariadb once a connection attempt is made? I believe the /etc/reviewboard/sites facility is unique to Fedora/EPEL, so this is could be a distro issue rather than ReviewBoard. Thanks, Paul -- 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.
Re: EPEL - rb-site upgrade failure upon reboot prevents httpd startup
On Wed, 2014-10-29 at 11:04 -0700, Paul Fee wrote: Hi all (and Stephen Gallagher), I'm using CentOS7 + EPEL with ReviewBoard-2.0.11 (fresh install + today's updates). My site is listed in /etc/reviewboard/sites. When httpd starts up, it checks if any sites need upgraded. I'm using a mariadb database. When I reboot the box, httpd fails to startup. $ sudo systemctl status httpd httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled) Drop-In: /usr/lib/systemd/system/httpd.service.d └─reviewboard-sites.conf Active: failed (Result: exit-code) since Wed 2014-10-29 17:42:28 GMT; 16s ago Process: 1184 ExecStartPre=/usr/bin/rb-site upgrade --all-sites (code=exited, status=1/FAILURE) Oct 29 17:42:28 centos7 rb-site[1184]: File /usr/lib/python2.7/site-packages/django/db/backends/mysql/base.py, line 435, in get_new_connection Oct 29 17:42:28 centos7 rb-site[1184]: conn = Database.connect(**conn_params) Oct 29 17:42:28 centos7 rb-site[1184]: File /usr/lib64/python2.7/site-packages/MySQLdb/__init__.py, line 81, in Connect Oct 29 17:42:28 centos7 rb-site[1184]: return Connection(*args, **kwargs) Oct 29 17:42:28 centos7 rb-site[1184]: File /usr/lib64/python2.7/site-packages/MySQLdb/connections.py, line 187, in __init__ Oct 29 17:42:28 centos7 rb-site[1184]: super(Connection, self).__init__(*args, **kwargs2) Oct 29 17:42:28 centos7 rb-site[1184]: django.db.utils.OperationalError: (2002, Can't connect to local MySQL server through socket '...k' (2)) Oct 29 17:42:28 centos7 systemd[1]: httpd.service: control process exited, code=exited status=1 Oct 29 17:42:28 centos7 systemd[1]: Failed to start The Apache HTTP Server. Oct 29 17:42:28 centos7 systemd[1]: Unit httpd.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. == I can manually start httpd as mariadb is now running by the time I've logged in. If I remove the /etc/reviewboard/sites file, the issue goes away. If I restore the file, the issue comes back. It looks like rb-site upgrade is being run before the database is available. Should systemd be using socket activation to start mariadb once a connection attempt is made? I believe the /etc/reviewboard/sites facility is unique to Fedora/EPEL, so this is could be a distro issue rather than ReviewBoard. MariaDB does not currently support socket-activation. What you need to do as a workaround right now is to add the following lines to /usr/lib/systemd/system/httpd.service.d/reviewboard-sites.conf: [Unit] After=postgresql.service mariadb.service mysql.service I'll roll this into the Fedora and EPEL packages. I hadn't thought of it previously. (Note: it's safe to list all of them on the After= line as this only controls ordering; it doesn't cause any of them to be started that would not already have been). Now I just have to hope that Apache never grows a dependency on a database... :) -- 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.
Re: EPEL - rb-site upgrade failure upon reboot prevents httpd startup
On Wed, 2014-10-29 at 16:27 -0400, Stephen Gallagher wrote: On Wed, 2014-10-29 at 11:04 -0700, Paul Fee wrote: Hi all (and Stephen Gallagher), I'm using CentOS7 + EPEL with ReviewBoard-2.0.11 (fresh install + today's updates). My site is listed in /etc/reviewboard/sites. When httpd starts up, it checks if any sites need upgraded. I'm using a mariadb database. When I reboot the box, httpd fails to startup. $ sudo systemctl status httpd httpd.service - The Apache HTTP Server Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled) Drop-In: /usr/lib/systemd/system/httpd.service.d └─reviewboard-sites.conf Active: failed (Result: exit-code) since Wed 2014-10-29 17:42:28 GMT; 16s ago Process: 1184 ExecStartPre=/usr/bin/rb-site upgrade --all-sites (code=exited, status=1/FAILURE) Oct 29 17:42:28 centos7 rb-site[1184]: File /usr/lib/python2.7/site-packages/django/db/backends/mysql/base.py, line 435, in get_new_connection Oct 29 17:42:28 centos7 rb-site[1184]: conn = Database.connect(**conn_params) Oct 29 17:42:28 centos7 rb-site[1184]: File /usr/lib64/python2.7/site-packages/MySQLdb/__init__.py, line 81, in Connect Oct 29 17:42:28 centos7 rb-site[1184]: return Connection(*args, **kwargs) Oct 29 17:42:28 centos7 rb-site[1184]: File /usr/lib64/python2.7/site-packages/MySQLdb/connections.py, line 187, in __init__ Oct 29 17:42:28 centos7 rb-site[1184]: super(Connection, self).__init__(*args, **kwargs2) Oct 29 17:42:28 centos7 rb-site[1184]: django.db.utils.OperationalError: (2002, Can't connect to local MySQL server through socket '...k' (2)) Oct 29 17:42:28 centos7 systemd[1]: httpd.service: control process exited, code=exited status=1 Oct 29 17:42:28 centos7 systemd[1]: Failed to start The Apache HTTP Server. Oct 29 17:42:28 centos7 systemd[1]: Unit httpd.service entered failed state. Hint: Some lines were ellipsized, use -l to show in full. == I can manually start httpd as mariadb is now running by the time I've logged in. If I remove the /etc/reviewboard/sites file, the issue goes away. If I restore the file, the issue comes back. It looks like rb-site upgrade is being run before the database is available. Should systemd be using socket activation to start mariadb once a connection attempt is made? I believe the /etc/reviewboard/sites facility is unique to Fedora/EPEL, so this is could be a distro issue rather than ReviewBoard. MariaDB does not currently support socket-activation. What you need to do as a workaround right now is to add the following lines to /usr/lib/systemd/system/httpd.service.d/reviewboard-sites.conf: [Unit] After=postgresql.service mariadb.service mysql.service I'll roll this into the Fedora and EPEL packages. I hadn't thought of it previously. (Note: it's safe to list all of them on the After= line as this only controls ordering; it doesn't cause any of them to be started that would not already have been). Now I just have to hope that Apache never grows a dependency on a database... :) Fedora 21: https://admin.fedoraproject.org/updates/FEDORA-2014-13850/ReviewBoard-2.0.11-2.fc21 EPEL 7: https://admin.fedoraproject.org/updates/ReviewBoard-2.0.11-2.el7 -- 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.
Power Pack 1.1 is released
Hey everyone, We just put out a release of Power Pack 1.1. Power Pack is our premium add-on to Review Board that offers PDF document review, GitHub Enterprise, and more. The new version of Power Pack adds a major new feature: Reports. Reports allow you to get deep insights into the performance of the code review process. More details are up on the announcement at https://www.reviewboard.org/news/2014/10/29/power-pack-1-1-released/ For more information on Power Pack, see https://www.reviewboard.org/powerpack/ -David -- 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.
Re: Startup problems
Me too! I got the same problem,help!! 在 2012年7月2日星期一UTC+8下午10时55分45秒，laxmi写道： Hi, I am having same issue. Please help. I installed ReviewBoard 1.6.9 on fedora 15. Post isntallation RB complaing about data direcotry setup and I get following error connecting to http://IP of the machine from remote or http://localhost from same machine. Checked the data folder and it is owned by user apache and Apache is runing as user apache. Please adive what else I need to check. Manual server updates required A recent upgrade requires manual updates to be made on this server. After these changes are made, you should restart your server. If you have any questions or problems, please contact us on our mailing list http://groups.google.com/group/reviewboard. Data directory changes Your site's data directory isn't properly set up. This directory is where Review Board will store various state and configuration needed to access repositories. Your data directory is currently at: /var/www/review.com/data Permission problems The data directory must be writable by the web server. On Linux/Unix/Mac, you can fix this by typing: $ sudo chown -R apache /var/www/review.com/data On Windows, right-click the data directory and change the ownership to apache. . drwxrwxrwx. 2 apache apache 4096 Jul 2 03:07 data -- 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.
Re: Startup problems
This thread is very old. Can you post a new one with full details on your version, OS, and what errors you're seeing? Christian On Wednesday, October 29, 2014, 永鑫 Q qiuyinglans...@gmail.com wrote: Me too! I got the same problem,help!! 在 2012年7月2日星期一UTC+8下午10时55分45秒，laxmi写道： Hi, I am having same issue. Please help. I installed ReviewBoard 1.6.9 on fedora 15. Post isntallation RB complaing about data direcotry setup and I get following error connecting to http://IP of the machine from remote or http://localhost from same machine. Checked the data folder and it is owned by user apache and Apache is runing as user apache. Please adive what else I need to check. Manual server updates required A recent upgrade requires manual updates to be made on this server. After these changes are made, you should restart your server. If you have any questions or problems, please contact us on our mailing list http://groups.google.com/group/reviewboard. Data directory changes Your site's data directory isn't properly set up. This directory is where Review Board will store various state and configuration needed to access repositories. Your data directory is currently at: /var/www/review.com/data Permission problems The data directory must be writable by the web server. On Linux/Unix/Mac, you can fix this by typing: $ sudo chown -R apache /var/www/review.com/data On Windows, right-click the data directory and change the ownership to apache. . drwxrwxrwx. 2 apache apache 4096 Jul 2 03:07 data -- 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 javascript:_e(%7B%7D,'cvml','reviewboard%2bunsubscr...@googlegroups.com'); . For more options, visit https://groups.google.com/d/optout. -- -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com -- 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.
Issue 3644 in reviewboard: API key for automation purposes
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 3644 by vlov...@gmail.com: API key for automation purposes https://code.google.com/p/reviewboard/issues/detail?id=3644 What version are you running? 2.0.5 It would be nice if there was a mechanism whereby a user could have automation keys added. API keys could be used to perform *most* actions except do things like add more API keys. Thus the password could be done securely a compromised API key could be revoked really easily. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3644 in reviewboard: API key for automation purposes
Comment #1 on issue 3644 by vlov...@gmail.com: API key for automation purposes https://code.google.com/p/reviewboard/issues/detail?id=3644 Also, I believe this removes the need for the username as well - the API key can uniquely securely identify a username/password pair. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3644 in reviewboard: API key for automation purposes
Updates: Status: Fixed Comment #2 on issue 3644 by trowb...@gmail.com: API key for automation purposes https://code.google.com/p/reviewboard/issues/detail?id=3644 This is actually already done, and will ship in 2.1. We don't yet have all the docs written, but you can see some of it at https://www.reviewboard.org/docs/manual/dev/webapi/2.0/authenticating/#token-based-authentication -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3644 in reviewboard: API key for automation purposes
Comment #3 on issue 3644 by vlov...@gmail.com: API key for automation purposes https://code.google.com/p/reviewboard/issues/detail?id=3644 Sweet. Can't wait. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Issue 3645 in reviewboard: Need a way to hide old non-submitted reviews
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 3645 by ehin...@gmail.com: Need a way to hide old non-submitted reviews https://code.google.com/p/reviewboard/issues/detail?id=3645 *** For customer support, please post to reviewbo...@googlegroups.com *** If you have a patch, please submit it to http://reviews.reviewboard.org/ *** *** Do not post confidential information in this enhancement request! What version are you running? 2.0.6 What's the URL of the page this enhancement relates to, if any? Describe the enhancement and the motivation for it. My Incoming To Me dashboard currently has a bunch of old reviews from people that are no longer at the company or have just forgotten about them. There's even one that's 6 months old. These reviews stay on my dashboard and I have no way to get rid of them because the submitter never marked them as 'submitted'. I need a way to hide reviews I no longer care about. What operating system are you using? What browser? Safari, OS X 10.10 Please provide any additional information below. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 2894 in reviewboard: Archive reviews
Comment #4 on issue 2894 by trowb...@gmail.com: Archive reviews https://code.google.com/p/reviewboard/issues/detail?id=2894 Issue 3645 has been merged into this issue. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3645 in reviewboard: Need a way to hide old non-submitted reviews
Updates: Status: Duplicate Mergedinto: 2894 Comment #1 on issue 3645 by trowb...@gmail.com: Need a way to hide old non-submitted reviews https://code.google.com/p/reviewboard/issues/detail?id=3645 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3313 in reviewboard: HTTP authentication is required, but cannot be used with --diff-filename=-
Comment #2 on issue 3313 by weberja...@gmail.com: HTTP authentication is required, but cannot be used with --diff-filename=- https://code.google.com/p/reviewboard/issues/detail?id=3313 I haven't had a chance to re-test it in the latest version, but I don't think that was the case. I originally reported the issue here: https://groups.google.com/forum/#!topic/reviewboard/-m1fhSLYspg and the response from Christian Hammond was: This error is a bit unclear, but it's referring to the web API's HTTP authentication. Some of this code changed, and it looks like the problem is that we're doing the check regarding --diff-filename=- too early, preventing the provided username/password from working. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3646 in reviewboard: RBTools API throws an exception trying to discard a review it created
Comment #1 on issue 3646 by chip...@gmail.com: RBTools API throws an exception trying to discard a review it created https://code.google.com/p/reviewboard/issues/detail?id=3646 DELETEs don't return a body, so it's more likely that there's a bug in RBTools where it's assuming it'll get one, and a JSON one at that. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3646 in reviewboard: RBTools API throws an exception trying to discard a review it created
Updates: Status: Duplicate Mergedinto: 3450 Comment #2 on issue 3646 by trowb...@gmail.com: RBTools API throws an exception trying to discard a review it created https://code.google.com/p/reviewboard/issues/detail?id=3646 This is already fixed in git and will ship in 0.6.3 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3450 in reviewboard: Successful delete calls made through API throw ValueError
Comment #4 on issue 3450 by trowb...@gmail.com: Successful delete calls made through API throw ValueError https://code.google.com/p/reviewboard/issues/detail?id=3450 Issue 3646 has been merged into this issue. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3646 in reviewboard: RBTools API throws an exception trying to discard a review it created
Comment #3 on issue 3646 by vlov...@gmail.com: RBTools API throws an exception trying to discard a review it created https://code.google.com/p/reviewboard/issues/detail?id=3646 Awesome. All the bugs I've been filing have already been fixed. Can't wait. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
