Re: 1.5 to 1.7 DB Migration
Hi Christian, Thanks for the quick reply. I tried taking applying the fix you mentioned and it allowed the db migration to go through. I'm getting two small errors now, which I'm not sure if it's related to the fix or not. The first is: [Tue Aug 13 18:28:13 2013] [error] File /usr/lib64/python2.6/logging/__init__.py, line 779, in emit [Tue Aug 13 18:28:13 2013] [error] msg = self.format(record) [Tue Aug 13 18:28:13 2013] [error] File /usr/lib64/python2.6/logging/__init__.py, line 657, in format [Tue Aug 13 18:28:13 2013] [error] return fmt.format(record) [Tue Aug 13 18:28:13 2013] [error] File /usr/lib64/python2.6/logging/__init__.py, line 442, in format [Tue Aug 13 18:28:13 2013] [error] s = self._fmt % record.__dict__ [Tue Aug 13 18:28:13 2013] [error] KeyError: 'request_info' which occurs when clicking around the ui on things like All Review Requests. The other error happens when trying to load the admin page for adding new groups and adding new repositories. The page freezes because /static/admin/js/SelectBox.37509c7e5ad5.js:16 becomes unresponsive. On Monday, August 12, 2013 11:25:38 AM UTC-7, Christian Hammond wrote: It should be this week. We've been working on a couple other changes that needed to go in, and the last of it are up for review now. You can also try applying this patch: https://reviews.reviewboard.org/r/4420/ Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mon, Aug 12, 2013 at 10:59 AM, Alvin .Feng alvin...@yahoo.comjavascript: wrote: Hi Christian, Thanks for the response. Is there any updates or eta on the fix yet? Thanks, Alvin On Tuesday, August 6, 2013 2:05:43 AM UTC-7, Christian Hammond wrote: Hi Alvin, This was reported recently, and I've been trying to figure out the best course of action. I expect to put out a release later this week with a fix. I recommend sticking to 1.5 for now, and upgrading once the new 1.7 is out. Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mon, Aug 5, 2013 at 6:52 PM, Alvin .Feng alvin...@yahoo.com wrote: Hi there, I currently have a Review Board 1.5 setup, and I'm trying to upgrade to 1.7. When I try to run the rb-site upgrade part to upgrade the database, I get the following error: File lib64/reviewboard/MySQL_**python-1.2.4-py2.6-linux-x86_** 64.egg/MySQLdb/connections.py**, line 36, in defaulterrorhandler raise errorclass, errorvalue django.db.utils.DatabaseError: (1071, 'Specified key was too long; max key length is 1000 bytes') I think the sql statement it is trying to execute is: CREATE TABLE `hostingsvcs_**hostingserviceaccount` ( `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY, `service_name` varchar(128) NOT NULL, `hosting_url` varchar(255), `username` varchar(128) NOT NULL, `data` longtext NOT NULL, `visible` bool NOT NULL, `local_site_id` integer, UNIQUE (`service_name`, `hosting_url`, `username`, `local_site_id`) ) ; I clean install reviewboard 1.7 on one host, and I try to connect it to the db host that was running with 1.5. Is there a way to just migrate the mysql db across versions? Any help would be appreciated. Thanks. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**donate/http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**users/http://www.reviewboard.org/users/ -~--~~~~--**~~--~--~--- To unsubscribe from this group, send email to reviewboard...@** googlegroups.com For more options, visit this group at http://groups.google.com/** group/reviewboard?hl=enhttp://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...@**googlegroups.com. For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out . -- 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...@googlegroups.com javascript: 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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- Want to help the Review
Re: 1.5 to 1.7 DB Migration
The only other items in the log are depreciation warnings related to django and other python modules. There's no other trackbacks. The thing most confusing to me about it is that I don't know what problems that error is creating. After migrating, there was an issue where pretty much every other page load would result in a 500 error, and I thought this was the root of that problem. Then 20 minutes later the 500 problem completely disappeared, but the logs are still showing this error on every page load. On Tuesday, August 13, 2013 11:57:31 AM UTC-7, Christian Hammond wrote: Can you show me what else is in the log file? I've seen this particular error as a side-effect of another crash. There should be a traceback right before this one. The SelectBox can be unresponsive for very large installations. I want to get rid of that and find a better solution beyond what Django ships... Roughly how many repositories and users do you have? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Tue, Aug 13, 2013 at 11:52 AM, Alvin .Feng alvin...@yahoo.comjavascript: wrote: Hi Christian, Thanks for the quick reply. I tried taking applying the fix you mentioned and it allowed the db migration to go through. I'm getting two small errors now, which I'm not sure if it's related to the fix or not. The first is: [Tue Aug 13 18:28:13 2013] [error] File /usr/lib64/python2.6/logging/__init__.py, line 779, in emit [Tue Aug 13 18:28:13 2013] [error] msg = self.format(record) [Tue Aug 13 18:28:13 2013] [error] File /usr/lib64/python2.6/logging/__init__.py, line 657, in format [Tue Aug 13 18:28:13 2013] [error] return fmt.format(record) [Tue Aug 13 18:28:13 2013] [error] File /usr/lib64/python2.6/logging/__init__.py, line 442, in format [Tue Aug 13 18:28:13 2013] [error] s = self._fmt % record.__dict__ [Tue Aug 13 18:28:13 2013] [error] KeyError: 'request_info' which occurs when clicking around the ui on things like All Review Requests. The other error happens when trying to load the admin page for adding new groups and adding new repositories. The page freezes because /static/admin/js/SelectBox.37509c7e5ad5.js:16 becomes unresponsive. On Monday, August 12, 2013 11:25:38 AM UTC-7, Christian Hammond wrote: It should be this week. We've been working on a couple other changes that needed to go in, and the last of it are up for review now. You can also try applying this patch: https://reviews.** reviewboard.org/r/4420/ https://reviews.reviewboard.org/r/4420/ Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mon, Aug 12, 2013 at 10:59 AM, Alvin .Feng alvin...@yahoo.comwrote: Hi Christian, Thanks for the response. Is there any updates or eta on the fix yet? Thanks, Alvin On Tuesday, August 6, 2013 2:05:43 AM UTC-7, Christian Hammond wrote: Hi Alvin, This was reported recently, and I've been trying to figure out the best course of action. I expect to put out a release later this week with a fix. I recommend sticking to 1.5 for now, and upgrading once the new 1.7 is out. Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mon, Aug 5, 2013 at 6:52 PM, Alvin .Feng alvin...@yahoo.comwrote: Hi there, I currently have a Review Board 1.5 setup, and I'm trying to upgrade to 1.7. When I try to run the rb-site upgrade part to upgrade the database, I get the following error: File lib64/reviewboard/MySQL_**pytho**n-1.2.4-py2.6-linux-x86_**64.* *egg/MySQLdb/connections.py**, line 36, in defaulterrorhandler raise errorclass, errorvalue django.db.utils.DatabaseError: (1071, 'Specified key was too long; max key length is 1000 bytes') I think the sql statement it is trying to execute is: CREATE TABLE `hostingsvcs_**hostingserviceacc**ount` ( `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY, `service_name` varchar(128) NOT NULL, `hosting_url` varchar(255), `username` varchar(128) NOT NULL, `data` longtext NOT NULL, `visible` bool NOT NULL, `local_site_id` integer, UNIQUE (`service_name`, `hosting_url`, `username`, `local_site_id`) ) ; I clean install reviewboard 1.7 on one host, and I try to connect it to the db host that was running with 1.5. Is there a way to just migrate the mysql db across versions? Any help would be appreciated. Thanks. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**don**ate/http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**use**rs/http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send
Re: 1.5 to 1.7 DB Migration
Hi Christian, Thanks for the response. Is there any updates or eta on the fix yet? Thanks, Alvin On Tuesday, August 6, 2013 2:05:43 AM UTC-7, Christian Hammond wrote: Hi Alvin, This was reported recently, and I've been trying to figure out the best course of action. I expect to put out a release later this week with a fix. I recommend sticking to 1.5 for now, and upgrading once the new 1.7 is out. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Mon, Aug 5, 2013 at 6:52 PM, Alvin .Feng alvin...@yahoo.comjavascript: wrote: Hi there, I currently have a Review Board 1.5 setup, and I'm trying to upgrade to 1.7. When I try to run the rb-site upgrade part to upgrade the database, I get the following error: File lib64/reviewboard/MySQL_python-1.2.4-py2.6-linux-x86_64.egg/MySQLdb/connections.py, line 36, in defaulterrorhandler raise errorclass, errorvalue django.db.utils.DatabaseError: (1071, 'Specified key was too long; max key length is 1000 bytes') I think the sql statement it is trying to execute is: CREATE TABLE `hostingsvcs_hostingserviceaccount` ( `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY, `service_name` varchar(128) NOT NULL, `hosting_url` varchar(255), `username` varchar(128) NOT NULL, `data` longtext NOT NULL, `visible` bool NOT NULL, `local_site_id` integer, UNIQUE (`service_name`, `hosting_url`, `username`, `local_site_id`) ) ; I clean install reviewboard 1.7 on one host, and I try to connect it to the db host that was running with 1.5. Is there a way to just migrate the mysql db across versions? Any help would be appreciated. Thanks. -- 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...@googlegroups.com javascript: 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...@googlegroups.com javascript:. For more options, visit https://groups.google.com/groups/opt_out. -- 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.
1.5 to 1.7 DB Migration
Hi there, I currently have a Review Board 1.5 setup, and I'm trying to upgrade to 1.7. When I try to run the rb-site upgrade part to upgrade the database, I get the following error: File lib64/reviewboard/MySQL_python-1.2.4-py2.6-linux-x86_64.egg/MySQLdb/connections.py, line 36, in defaulterrorhandler raise errorclass, errorvalue django.db.utils.DatabaseError: (1071, 'Specified key was too long; max key length is 1000 bytes') I think the sql statement it is trying to execute is: CREATE TABLE `hostingsvcs_hostingserviceaccount` ( `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY, `service_name` varchar(128) NOT NULL, `hosting_url` varchar(255), `username` varchar(128) NOT NULL, `data` longtext NOT NULL, `visible` bool NOT NULL, `local_site_id` integer, UNIQUE (`service_name`, `hosting_url`, `username`, `local_site_id`) ) ; I clean install reviewboard 1.7 on one host, and I try to connect it to the db host that was running with 1.5. Is there a way to just migrate the mysql db across versions? Any help would be appreciated. Thanks. -- 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: Unable to access the root /api/ URL on the server.
Exactly. It works now. Thanks a lot.
By the way, I could not attach the difference when posting a review.
I have created another post for this problem.
On 10月30日, 下午3時39分, Christian Hammond chip...@chipx86.com wrote:
Do you generally use a proxy server? It could be that you're going through
the proxy, which means you're not accessing what you expect.
You could try using --disable-proxy to check.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -http://www.reviewboard.org
VMware, Inc. -http://www.vmware.com
On Mon, Oct 29, 2012 at 9:45 PM, Alvin NG asang...@gmail.com wrote:
Hi,
I'm trying to create a review on top of a commit in a svn repository.
However, I got the following error.
But if I accesshttp://127.0.0.1/reviewboard/api/directly via
browser, I could get the file.
---
---
[Error]
post-review --server=http://127.0.0.1/reviewboard--debug RBTools
0.4.2
Python 2.6 (r26:66714, May 6 2011, 15:21:49)
[GCC 4.3.4 [gcc-4_3-branch revision 152973]]
Running on Linux-3.0.13-0.27-default-i686-with-SuSE-11-i586
Home = /root
Current Directory = /usr/proj
Checking the repository type. Errors shown below are mostly harmless.
DEBUG:root:Checking for a CVS repository...
DEBUG:root:Checking for a ClearCase repository...
DEBUG:root:Checking for a Git repository...
DEBUG:root:Running: git rev-parse --git-dir
DEBUG:root:Command exited with rc 128: ['git', 'rev-parse', '--git-
dir']
fatal: Not a git repository (or any of the parent directories): .git
---
DEBUG:root:Checking for a Mercurial repository...
DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Checking for a Plastic repository...
DEBUG:root:Checking for a Subversion repository...
DEBUG:root:Running: svn info
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: svn://127.0.0.1, Base path: /,
Supports changesets: False
Finished checking the repository type.
HTTP GETting api/
Got HTTP error: 400: HTMLHEAD
TITLERequest Error/TITLE
/HEAD
BODY
FONT face=Helvetica
bigstrong/strong/bigBR
/FONT
blockquote
TABLE border=0 cellPadding=1 width=80%
TRTD
FONT face=Helvetica
bigRequest Error (invalid_request)/big
BR
BR
/FONT
/TD/TR
TRTD
FONT face=Helvetica
Your request could not be processed. Request could not be handled
/FONT
/TD/TR
TRTD
FONT face=Helvetica
This could be caused by a misconfiguration, or possibly a malformed
request.
/FONT
/TD/TR
TRTD
FONT face=Helvetica SIZE=2
BR
For assistance, contact your network support team.
/FONT
/TD/TR
/TABLE
/blockquote
/FONT
/BODY/HTML
Unable to access the root /api/ URL on the server.
---
---
[http://127.0.0.1/reviewboard/api/]
?xml version=1.0 encoding=utf-8?
rsp
statok/stat
uri_templates
diff_commentshttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/{review_id}/replies/{reply_id}/diff-
comments//diff_comments
watched_review_groupshttp://127.0.0.1/reviewboard/api/users/
{username}/watched/review-groups//watched_review_groups
sessionhttp://127.0.0.1/reviewboard/api/session//session
file_attachmentshttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/file-attachments//file_attachments
filehttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/diffs/{diff_revision}/files/{filediff_id}//file
replieshttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/{review_id}/replies//replies
diffhttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/diffs/{diff_revision}//diff
screenshotshttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/screenshots//screenshots
watched_review_requesthttp://127.0.0.1/reviewboard/api/users/
{username}/watched/review-requests/{watched_obj_id}//
watched_review_request
grouphttp://127.0.0.1/reviewboard/api/groups/{group_name}//group
screenshothttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/screenshots/{screenshot_id}//screenshot
reviewhttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/{review_id}//review
watched_review_grouphttp://127.0.0.1/reviewboard/api/users/
{username}/watched/review-groups/{watched_obj_id}//
watched_review_group
last_updatehttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/last-update//last_update
diff_commenthttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/{review_id}/replies/{reply_id}/diff-
comments/{comment_id}//diff_comment
drafthttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/draft//draft
post-review: Error uploading diff
Hi, I could not attach the difference between revisions to my review. It gives me the error Got API Error 105 (HTTP code 400): One or more fields had errors. I have also tried to output the difference by using svn diff and attach the file to my review, but it still gives me the same error. My command: post-review --server=http://localhost/reviewboard --debug --disable-proxy --target-group=proj_test -- revision=0:11 --diff- filename=diff.txt (I'm not sure if this would also help) The repository server of my Reviewboard is like this svn://localhost/test_proj but not the local path to the reviewboard server Many thanks, Alvin -- 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: post-review: Error uploading diff
test_proj is the root of the SVN server. I kick my SVN server by svnserve -d -r /svn/test_proj/ On 10月30日, 下午4時47分, Christian Hammond chip...@chipx86.com wrote: Make sure Review Board is configured to point to the root of the SVN server, not a subdirectory within. I'm assuming test_proj is a subdirectory inside the repo? Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Tue, Oct 30, 2012 at 1:44 AM, Alvin NG asang...@gmail.com wrote: Hi, I could not attach the difference between revisions to my review. It gives me the error Got API Error 105 (HTTP code 400): One or more fields had errors. I have also tried to output the difference by using svn diff and attach the file to my review, but it still gives me the same error. My command: post-review --server=http://localhost/reviewboard--debug --disable-proxy --target-group=proj_test -- revision=0:11 --diff- filename=diff.txt (I'm not sure if this would also help) The repository server of my Reviewboard is like this svn://localhost/test_proj but not the local path to the reviewboard server Many thanks, Alvin -- 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: post-review: Error uploading diff
FYI, here is the setting in my reviewboard Path: svn://localhost Mirror path: (empty) I saw a post which is talking about the same problem (I think) here https://groups.google.com/group/reviewboard/browse_thread/thread/d770407ab6d34fb8/923d3f8b7de4d85a I followed the setting suggested by the above post and set Path: /svn/test_proj Mirror path: svn@server:localhost But it still doesn't work. Hope this would help. On 10月30日, 下午4時47分, Christian Hammond chip...@chipx86.com wrote: Make sure Review Board is configured to point to the root of the SVN server, not a subdirectory within. I'm assuming test_proj is a subdirectory inside the repo? Christian -- Christian Hammond - chip...@chipx86.com Review Board -http://www.reviewboard.org VMware, Inc. -http://www.vmware.com On Tue, Oct 30, 2012 at 1:44 AM, Alvin NG asang...@gmail.com wrote: Hi, I could not attach the difference between revisions to my review. It gives me the error Got API Error 105 (HTTP code 400): One or more fields had errors. I have also tried to output the difference by using svn diff and attach the file to my review, but it still gives me the same error. My command: post-review --server=http://localhost/reviewboard--debug --disable-proxy --target-group=proj_test -- revision=0:11 --diff- filename=diff.txt (I'm not sure if this would also help) The repository server of my Reviewboard is like this svn://localhost/test_proj but not the local path to the reviewboard server Many thanks, Alvin -- 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
Unable to access the root /api/ URL on the server.
Hi,
I'm trying to create a review on top of a commit in a svn repository.
However, I got the following error.
But if I access http://127.0.0.1/reviewboard/api/ directly via
browser, I could get the file.
--
[Error]
post-review --server=http://127.0.0.1/reviewboard --debug RBTools
0.4.2
Python 2.6 (r26:66714, May 6 2011, 15:21:49)
[GCC 4.3.4 [gcc-4_3-branch revision 152973]]
Running on Linux-3.0.13-0.27-default-i686-with-SuSE-11-i586
Home = /root
Current Directory = /usr/proj
Checking the repository type. Errors shown below are mostly harmless.
DEBUG:root:Checking for a CVS repository...
DEBUG:root:Checking for a ClearCase repository...
DEBUG:root:Checking for a Git repository...
DEBUG:root:Running: git rev-parse --git-dir
DEBUG:root:Command exited with rc 128: ['git', 'rev-parse', '--git-
dir']
fatal: Not a git repository (or any of the parent directories): .git
---
DEBUG:root:Checking for a Mercurial repository...
DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Checking for a Plastic repository...
DEBUG:root:Checking for a Subversion repository...
DEBUG:root:Running: svn info
DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: svn://127.0.0.1, Base path: /,
Supports changesets: False
Finished checking the repository type.
HTTP GETting api/
Got HTTP error: 400: HTMLHEAD
TITLERequest Error/TITLE
/HEAD
BODY
FONT face=Helvetica
bigstrong/strong/bigBR
/FONT
blockquote
TABLE border=0 cellPadding=1 width=80%
TRTD
FONT face=Helvetica
bigRequest Error (invalid_request)/big
BR
BR
/FONT
/TD/TR
TRTD
FONT face=Helvetica
Your request could not be processed. Request could not be handled
/FONT
/TD/TR
TRTD
FONT face=Helvetica
This could be caused by a misconfiguration, or possibly a malformed
request.
/FONT
/TD/TR
TRTD
FONT face=Helvetica SIZE=2
BR
For assistance, contact your network support team.
/FONT
/TD/TR
/TABLE
/blockquote
/FONT
/BODY/HTML
Unable to access the root /api/ URL on the server.
--
[http://127.0.0.1/reviewboard/api/ ]
?xml version=1.0 encoding=utf-8?
rsp
statok/stat
uri_templates
diff_commentshttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/{review_id}/replies/{reply_id}/diff-
comments//diff_comments
watched_review_groupshttp://127.0.0.1/reviewboard/api/users/
{username}/watched/review-groups//watched_review_groups
sessionhttp://127.0.0.1/reviewboard/api/session//session
file_attachmentshttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/file-attachments//file_attachments
filehttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/diffs/{diff_revision}/files/{filediff_id}//file
replieshttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/{review_id}/replies//replies
diffhttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/diffs/{diff_revision}//diff
screenshotshttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/screenshots//screenshots
watched_review_requesthttp://127.0.0.1/reviewboard/api/users/
{username}/watched/review-requests/{watched_obj_id}//
watched_review_request
grouphttp://127.0.0.1/reviewboard/api/groups/{group_name}//group
screenshothttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/screenshots/{screenshot_id}//screenshot
reviewhttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/{review_id}//review
watched_review_grouphttp://127.0.0.1/reviewboard/api/users/
{username}/watched/review-groups/{watched_obj_id}//
watched_review_group
last_updatehttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/last-update//last_update
diff_commenthttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/{review_id}/replies/{reply_id}/diff-
comments/{comment_id}//diff_comment
drafthttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/draft//draft
replyhttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/{review_id}/replies/{reply_id}//reply
review_requesthttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}//review_request
fileshttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/diffs/{diff_revision}/files//files
review_drafthttp://127.0.0.1/reviewboard/api/review-requests/
{review_request_id}/reviews/draft//review_draft
usershttp://127.0.0.1/reviewboard/api/users//users
repositoryhttp://127.0.0.1/reviewboard/api/repositories/
{repository_id}//repository
file_attachment_commentshttp://127.0.0.1/reviewboard/api/review-
requests/{review_request_id}/file-attachments/{file_attachment_id}/
file-attachment-comments//file_attachment_comments
watchedhttp://127.0.0.1/reviewboard/api/users/{username}/watched//
Re: Email Settings
well... i figured that one out. The problem is that I'm using post-review from a subversion hook with the --submit-as option. And the dedicated user was not assigned a Name / email and therefore will default to webmas...@localhost. On Fri, Aug 28, 2009 at 3:08 PM, dartarrow dartar...@gmail.com wrote: Hey, how do i set the FROM email address? I have exim4 setup on my localhost which send the email from webmas...@localhost I would like to change that to something like reviewbo...@mycompany.com Thanks --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups reviewboard group. To post to this group, send email to reviewboard@googlegroups.com 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 -~--~~~~--~~--~--~---
