Broken Link on Main Page
Hi, the link to the Python API on the main page (http://www.reviewboard.org) is broken: http://www.reviewboard.org/docs/rbtools/dev/api/ Regards Ruben -- 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: What's the usage of the Edit box on middle right of the window?
Hi, to use the search functionality there are some prerequisites listed here: http://www.reviewboard.org/docs/manual/1.6/admin/sites/search-indexing/ Regards, Ruben From: 深圳手机 (王) 825772...@qq.commailto:825772...@qq.com Reply-To: reviewboard@googlegroups.commailto:reviewboard@googlegroups.com Date: Tue, 6 Mar 2012 11:24:16 +0800 To: reviewboard reviewboard@googlegroups.commailto:reviewboard@googlegroups.com Subject: What's the usage of the Edit box on middle right of the window? There is an Edit box on middle right of the window, In the manual, it says it's quick search, but it seems it can't search anything, you can type words in it , but no result even you type enter key or click mouse. what 's the matter? -- 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: How can I get the submitter of the review request by Web API?
Hi richer,
assuming your question is related to a current 1.6.X-release - have you
tried to find your answer in the Web-API documentation?
http://www.reviewboard.org/docs/manual/1.6/webapi/2.0/resources/review-requ
est/
The Review Request Resource, which you reach by the link described there:
{revieboard-url}/api/review-requests/{review_request_id}/
contains a field named submitter, which yields a User Resource from
which you may read the information about the submitter you want:
http://www.reviewboard.org/docs/manual/1.6/webapi/2.0/resources/user/#webap
i2.0-user-resource
Regards, Ruben
--
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
ReviewBoard Icon Trademark
Good Morning, I would like to create some icons for our installation's reminder E-Mails based on ReviewBoard's pin board logo. Looking at the software's license I guess I am free to do so. However, I just noticed the TM marker next to the logo on your main page reviewboard.org. So I guess there is a registration progress ongoing for ReviewBoard as trademark? Does this include the logo or just the name and slogan? In summary: Am I allowed to create some icons based on the pin board logo? If so - I will post them on this list as soon as they are finished. Regards, Ruben -- 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: What's the mean of ship it!?
Hi, as far as I know it is the latter. Since the default workflow design for ReviewBoard is to review the code before it is committed, clicking on ship it! means to tell the author: Yes, I agree to your changes: Ship it! At this, to ship has the meaning of sending or committing the suggested changes to the VCS. Regards, Ruben From: 深圳手机 (王) 825772...@qq.commailto:825772...@qq.com Reply-To: reviewboard@googlegroups.commailto:reviewboard@googlegroups.com Date: Tue, 14 Feb 2012 17:33:18 +0800 To: reviewboard reviewboard@googlegroups.commailto:reviewboard@googlegroups.com Subject: What's the mean of ship it!? What's the mean of ship it!? I am puzzled for this question for some time. Remind the people don't forget to review the code? or the reviewer accept the result? -- 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.commailto: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: Repository/project name in the email request
Hi Elardus,
you can simply add what you want to display in an E-Mail by editing the
corresponding template file(s) of your reviewboard installation. For
example for new review requests:
reviewboard/template/notifications/review_request_email.html/.txt
For all types of messages sent there is such a template. Inside these
templates you can refer to dynamic data by using django tags. The one you
want is probably {{review_request.repository}}.
If you want that information in the subject you can edit the corresponding
code in reviewboard/notifications/email.py.
Regards, Ruben
On 2011-11-28 14:41, elard...@digicore.co.za wrote:
I set up a ReviewBoard server and we are starting to use it now.
However, we have many repositories set up on it (20+) and the review
emails do not state the repository/project the email pertains to.
Therefore it is difficult by just looking at the review request to
know which project it relates to.
Is it possible to add this functionality somehow?
--
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: SIGSEGV inside pylucene
Hello, I got some more information from the PyLucene mailing-list. On 2011-10-25 10:52, va...@apache.org wrote: Hi, The usual problem with embedding a Python extension built with JCC in an Apache process - which I guess is what you are doing - is that the process and threads where JCC is used in not properly initialized: - initVM() must be called from the main thread before any Java call can be made. - other threads must call attachCurrentThread() before they can make any Java call. Andi.. Calling the thread function can be done with: lucene.getVMEnv().attachCurrentThread() However, I am not shure where to put this call. Furthermore I found two spots where initVM is called, and I am also unsure whether those lines get executed in the main thread or in an additional thread. initVM() is found in: reviewboard/reviews/views.py reviewboard/reviews/management/commands/index.py Can anyone help me to dig deeper on this threading issue? Regards, Ruben -- 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: SIGSEGV inside pylucene
Hello again, I now solved the issue by calling the right initializations of PyLucene (after some trial): 1. Add import lucene and lucene.initVM(lucene.CLASSPATH) to the top of your reviewboard/settings.py file. This ensures that the VM is initialized in the main thread. 2. Add the statment lucene.getVMEnv().attachCurrentThread() right behind the import lucene statement in reviewboard/reviews/views.py. This is necessary to attach each new thread which uses the VM. After doing this the SIGSEGV errors with apache2 went away. Maybe there is a better spot to put those things, but it should be definitely adjusted for further releases. Regards, Ruben -- 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
SIGSEGV inside pylucene
Hello, I was tinkering with the search function of ReviewBoard for some time now. I got it to run, but it is quite unusable since almost every query results in a Review Board is taking a nap page being shown. After some time then (one minute I guess?) ReviewBoard answers with No requests matching your query: (No matter if there would be a result normally). I looked into the apache2-log and found a strange error: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fab1f777874, pid=16468, tid=140373040924416 # # JRE version: 6.0_26-b03 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libjcc.so+0x7874] JCCEnv::setClassPath(char const*)+0x24 # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp I found one user reporting the same, strange behavior within another function: http://groups.google.com/group/reviewboard/browse_thread/thread/86f8eb35dc9 15652/9380fca82aaaefa3 Is there any recent wisdom about what is wrong with my setup? I recently built a recent pylucene manually and swapped the open-jdk with sun's jdk without any result. Regards, Ruben ReviewBoard: 1.6.1 Pylucene: 3.4.0-1 (also tried 2.3.1-1.1u from aptitude) Python: 2.6.5 --- S Y S T E M --- OS:squeeze/sid uname:Linux 2.6.32-22-server #36-Ubuntu SMP Thu Jun 3 20:38:33 UTC 2010 x86_64 libc:glibc 2.11.1 NPTL 2.11.1 rlimit: STACK 8192k, CORE 0k, NPROC infinity, NOFILE 1024, AS infinity load average:0.51 0.66 0.53 CPU:total 1 (1 cores per cpu, 1 threads per core) family 6 model 23 stepping 8, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1 Memory: 4k page, physical 505492k(65320k free), swap 2095096k(1992788k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (20.1-b02) for linux-amd64 JRE (1.6.0_26-b03), built on May 4 2011 01:13:47 by java_re with gcc 3.2.2 (SuSE Linux) -- 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
Download file dialog instead of the expected review board page
Hello, I have a sporadically appearing problem with ReviewBoard 1.5.4. Sometimes when I click any link inside ReviewBoard I suddenly get a download dialog for a raw file from my browser. If the link would change a state (e.g. clicked a save button inside a settings dialog) the expected action (saving the settings) is done, but I don't see the expected result page. Instead FireFox shows a dialog for downloading a raw file. The file contains a HTTP header and runes after that. For instance clicking on a link to my dashboard resulted recently in a download dialog for the file Ra+wZN13.dms-1.part containing this header followed by many runes: HTTP/1.1 200 OK Date: Mon, 28 Mar 2011 11:50:47 GMT Server: Apache/2.2.14 (Ubuntu) Content-Length: 5298 Content-Language: en-us Content-Encoding: gzip Vary: Cookie,Accept-Language,Accept-Encoding Keep-Alive: timeout=15, max=99 Connection: Keep-Alive Content-Type: text/html; charset=utf-8 I am using: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.16) Gecko/20110319 Firefox/3.6.16 Is this a configuration issue of my server? Does anyone have an idea what I can do to avoid it? It is only a small nuisance as reloading the page gets you to the desired result, but my users are confused about that. Regards, Ruben smime.p7s Description: S/MIME cryptographic signature
Re: post-review from windows fails
On 15.03.2011, at 21:46, Christian Hammond wrote:
Are you behind a proxy server?
No, I am not behind a proxy server.
With 0.3.2, can you run with --debug and provide the output?
The output is attached as debug_output_rbtools_0.3.2.txt
I can report some details concerning the problem:
1. While playing around with the login problems I found out, that
allowing anonymous read access brings post-review some steps further,
but then again it stops asking for Web-API credentials although user
name and password were provided via command line. See
debug_output_anonymous_read.txt for the output.
2. The behavior of post-review 0.2 on osx does not differ from the one
on windows, that was wrong. The difference resulted from the fact,
that I had a valid cookie in my .postreview-cookies.txt on osx. As
soon as I copy that cookie to the windows machine, I can authenticate
there as well.
3. With the valid cookie in my .postreview-cookies.txt file it seems
to to ignore any credentials on the command line. I start pushing a
diff-file with a --username= argument, but without password. post-
review then prompts for a password, as expected. But no matter what I
type there, the operation will always succeed due to the cookie. Does
review-board use the cookie as fallback authentication method if the
password is false? I would expect the operation to fail if I provide a
specific user name and an invalid password is typed. Maybe this is
related to this older bug:
http://code.google.com/p/reviewboard/issues/detail?id=762
See debug_output_withoutcookie.txt for an example.
4. My normal authentication mechanism is ActiveDirectory. Changing back to
standard authentication does not solve the problem.
Sorry for re-posting the message, I think I tamed the mail-client now.
Regards, Ruben
--
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=enC:\Promptpost-review --submit-as=username --target-groups= --target-
people=targetuser --diff-filename=rbDiff_File --repository-url=https://
subversion.lan/dev --bugs-closed= --
summary=file.ending/.otherending@revision --description=asdf --
server=http://reviewboard.lan --username=admin --publish --debug
RBTools 0.3.2
Home = C:\Users\rstein.MR\AppData\Roaming
svn info https://subversion.lan/dev
diff --version
repository info: Path: https://subversion.lan/dev, Base path: /, Suppor
ts changesets: False
HTTP GETting api/
== HTTP Authentication Required
Enter authorization information for Web API at reviewboard.fme.lan
Password:
HTTP GETting http://reviewboard.lan/api/info/
Using the new web API
HTTP GETting http://reviewboard.lan/api/repositories/
HTTP GETting http://reviewboard.lan/api/repositories/1/
HTTP GETting http://reviewboard.lan/api/repositories/1/info/
HTTP GETting http://reviewboard.lan/api/repositories/2/
HTTP GETting http://reviewboard.lan/api/repositories/2/info/
repository info: Path: https://subversion.lan/dev, Base path: /, Suppor
ts changesets: False
Attempting to create review request on https://subversion.lan/dev for N
one
Submitting the review request as rstein
HTTP POSTing to http://reviewboard.lan/api/review-requests/: {'submit_as
': 'rstein', 'repository': u'https://subversion.lan/dev'}
Review request created
Attempting to set field 'target_people' to 'targetuser' for review request
'127'
HTTP PUTting to http://reviewboard.lan/api/review-requests/127/draft/: {
'target_people': 'admin,rstein'}
Attempting to set field 'summary' to 'file.ending/.otherending@revision' f
or review request '127'
HTTP PUTting to http://reviewboard.lan/api/review-requests/127/draft/: {
'summary': 'file.ending/.otherending@revision'}
Attempting to set field 'description' to 'asdf' for review request '127'
HTTP PUTting to http://reviewboard.fme.lan/api/review-requests/127/draft/: {
'description': 'asdf'}
Uploading diff, size: 2838
HTTP POSTing to http://reviewboard.lan/api/review-requests/127/diffs/: {
'basedir': '/'}
Publishing
HTTP PUTting to http://reviewboard.lan/api/review-requests/127/draft/: {
'public': 1}
Review request #127 posted.
http://reviewboard.lan/r/127/ C:\Promptpost-review --submit-as=username --target-groups= --target-
people=targetuser --diff-filename=rbDiff_File --repository-url=https://
subversion.lan/dev --bugs-closed= --
summary=file.ending/.otherending@revision --description=asdf --
server=http://reviewboard.lan --username=dummyUser --
password=DummyPasswd --publish --debug
RBTools 0.3.2
Home = C:\Prompt
svn info https://suversion.landev
diff --version
repository info: Path: https://suversion.lan/dev, Base path: /, Suppor
ts changesets: False
HTTP GETting api/
HTTP GETting
Re: Setting target-groups or target-people with post-review fails
Hello again, I now realized, that only the user set with --submit-as can see the real content of the review-request draft. I was able to see only those submitted as admin correctly, because I was logged in as admin. But what is the reason for this? Are the fields stored user-local until the review is published? I think it is strange to show the admin a publish review button that publishes a completely different review-request than the user intended to post. At least admins should see the submitted fields, should they not? Regards, Ruben -- 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 from windows fails
On 15.03.2011, at 21:46, Christian Hammond wrote:
Are you behind a proxy server? If so, it's possible that post-review is
picking up the proxy settings on Windows, and it's preventing it from
accessing the site correctly.
No, I am not behind a proxy server.
With 0.3.2, can you run with --debug and provide the output?
The output is attached as debug_output_rbtools_0.3.2.txt
--
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=enC:\Promptpost-review --submit-as=username --target-groups= --target-
people=targetuser --diff-filename=rbDiff_File --repository-url=https://
subversion.lan/dev --bugs-closed= --
summary=file.ending/.otherending@revision --description=asdf --
server=http://reviewboard.lan --username=dummyUser --
password=DummyPasswd --publish --debug
RBTools 0.3.2
Home = C:\Prompt
svn info https://subversion/dev
diff --version
repository info: Path: https://subversion/dev, Base path: /, Suppor
ts changesets: False
HTTP GETting api/
HTTP GETting http://reviewboard.lan/api/info/
Got API Error 103 (HTTP code 401): You are not logged in
Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', u'
code': 103}}
Unable to access the root /api/ URL on the server.
I can report some details concerning the problem:
1. While playing around with the login problems I found out, that
allowing anonymous read access brings post-review some steps further,
but then again it stops asking for Web-API credentials although user
name and password were provided via command line. See
debug_output_anonymous_read.txt for the output.
C:\Promptpost-review --submit-as=username --target-groups= --target-
people=targetuser --diff-filename=rbDiff_File --repository-url=https://
subversion.lan/dev --bugs-closed= --
summary=file.ending/.otherending@revision --description=asdf --
server=http://reviewboard.lan --username=dummyUser --
password=DummyPasswd --publish --debug
RBTools 0.3.2
Home = C:\Prompt
svn info https://suversion.landev
diff --version
repository info: Path: https://suversion.lan/dev, Base path: /, Suppor
ts changesets: False
HTTP GETting api/
HTTP GETting http://reviewboard.lan/api/info/
Using the new web API
HTTP GETting http://reviewboard.lan/api/repositories/
HTTP GETting http://reviewboard.lan/api/repositories/1/
HTTP GETting http://reviewboard.lan/api/repositories/1/info/
HTTP GETting http://reviewboard.lan/api/repositories/2/
HTTP GETting http://reviewboard.lan/api/repositories/2/info/
repository info: Path: https://suversion.lan/dev, Base path: /, Suppor
ts changesets: False
Attempting to create review request on https://subversion.lan/dev for N
one
Submitting the review request as rstein
HTTP POSTing to http://reviewboard.lan/api/review-requests/: {'submit_as
': 'rstein', 'repository': u'https://subversion.lan/dev'}
Got API Error 103 (HTTP code 401): You are not logged in
Error data: {u'stat': u'fail', u'err': {u'msg': u'You are not logged in', u'
code': 103}}
Attempting to create review request on https://subversion.lan/dev for N
one
Submitting the review request as rstein
HTTP POSTing to http://reviewboard.lan/api/review-requests/: {'submit_as
': 'username', 'repository': u'https://subversion/dev'}
== HTTP Authentication Required
Enter authorization information for Web API at reviewboard.lan
Username: username
Password:
2. The behavior of post-review 0.2 on osx does not differ from the one
on windows, that was wrong. The difference resulted from the fact,
that I had a valid cookie in my .postreview-cookies.txt on osx. As
soon as I copy that cookie to the windows machine, I can authenticate
there as well.
3. With the valid cookie in my .postreview-cookies.txt file it seems
to to ignore any credentials on the command line. I start pushing a
diff-file with a --username= argument, but without password. post-
review then prompts for a password, as expected. But no matter what I
type there, the operation will always succeed due to the cookie. Does
review-board use the cookie as fallback authentication method if the
password is false? I would expect the operation to fail if I provide a
specific user name and an invalid password is typed. Maybe this is
related to this older bug:
http://code.google.com/p/reviewboard/issues/detail?id=762
See debug_output_withoutcookie.txt for an example.
C:\Promptpost-review --submit-as=username --target-groups= --target-
people=targetuser --diff-filename=rbDiff_File --repository-url=https://
subversion.lan/dev --bugs-closed= --
summary=file.ending/.otherending@revision --description=asdf --
server=http://reviewboard.lan --username=admin --publish --debug
RBTools 0.3.2
Home =
Setting target-groups or target-people with post-review fails
Hello,
I just realized, that no other user can use the --target-groups or
--target-people parameter if he does not also provide the --publish parameter.
More precisely my default user can't set any details of a review-request which
is passed without --publish to post-review. The resulting request is present in
the system, but all fields are empty and no diff is attached. However, if I add
--publish to the same command-line, all fields get changed and the request
looks like intended.
The weird thing about all that is, that if I set the original admin user
(created during setup process) via the --submit-as parameter, then the values
are set even without --publish.
I attached a log file, which shows post-review's output when the normal user
wants to upload a diff without --publish. The user has the following rights:
reviews | review request | Can add review request
reviews | review request | Can edit review request
reviews | review request | Can submit as another user
My Versions:
RBTools 0.3.2
ReviewBoard 1.5.4
I also tested another Reviewboard 1.5.1 installation, which shows the same
behavior.
Regards, Ruben
--
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=enpost-review --submit-as=reman --target-groups=group --target-people=person
--diff-filename=/var/folders/gt/gtQqtk9YGhKv-A-SpkbdKk+++TI/-Tmp-/rbDiff.file
--repository-url=https://subversion/dev --summary=summary --description=asdf
--server=http://reviewboard.lan --debug
RBTools 0.3.2
Home = /Users/user
svn info https://subversion/dev
diff --version
repository info: Path: https://subversion/dev, Base path: /, Supports
changesets: False
HTTP GETting api/
HTTP GETting http://reviewboard.lan/api/info/
Using the new web API
HTTP GETting http://reviewboard.lan/api/repositories/
HTTP GETting http://reviewboard.lan/api/repositories/1/
HTTP GETting http://reviewboard.lan/api/repositories/1/info/
HTTP GETting http://reviewboard.lan/api/repositories/2/
HTTP GETting http://reviewboard.lan/api/repositories/2/info/
repository info: Path: https://subversion/dev, Base path: /, Supports
changesets: False
Attempting to create review request on https://subversion/dev for None
Submitting the review request as reman
HTTP POSTing to http://reviewboard.lan/api/review-requests/: {'submit_as':
'reman', 'repository': u'https://subversion/dev'}
Review request created
Attempting to set field 'target_groups' to 'group' for review request '159'
HTTP PUTting to http://reviewboard.lan/api/review-requests/159/draft/:
{'target_groups': 'group'}
Attempting to set field 'target_people' to 'person' for review request '159'
HTTP PUTting to http://reviewboard.lan/api/review-requests/159/draft/:
{'target_people': 'person'}
Attempting to set field 'summary' to 'summary' for review request '159'
HTTP PUTting to http://reviewboard.lan/api/review-requests/159/draft/:
{'summary': 'summary'}
Attempting to set field 'description' to 'asdf' for review request '159'
HTTP PUTting to http://reviewboard.lan/api/review-requests/159/draft/:
{'description': 'asdf'}
Uploading diff, size: 4527
HTTP POSTing to http://reviewboard.lan/api/review-requests/159/diffs/:
{'basedir': '/'}
Review request #159 posted.
http://reviewboard.lan/r/159/
