ReviewBoard not displaying content of diff file

I have just started trying out reviewboard and I have some issues with some diffs not beeing displayed when I click View diff in the review request. When i download the diff I can see the content: Index: //trunk/library/extras/global-post-commit-hook.php

Re: 1.0.8 - 1.5 upgrade issues with repository management

Thanks a lot! Removing this tool solved the issues. I've added it a year ago trying to setup demo and forgot about that. -- Sergey On Oct 13, 8:41 am, Christian Hammond chip...@chipx86.com wrote: It sounds like you have the localfile scmtool installed in your database, which is really only for

Re: starting review #

Just to clarify: yes, this is on creating a rreview draft, so there should be no email involved. The user's browser is shown the Server Error (code 500) page, and the following entry is made in the Transfer/ Apache log: 10.xx.yy.29 - - [11/Oct/2010:20:03:22 -0700] POST /r/new/ HTTP/1.1

Re: ReviewBoard not displaying content of diff file

cogo wrote: I have just started trying out reviewboard and I have some issues with some diffs not beeing displayed when I click View diff in the review request. When i download the diff I can see the content: Index: //trunk/library/extras/global-post-commit-hook.php

ReviewBoard 1.5 under Apache: IOError when posting review from command line post-review tool

Starting in ReviewBoard 1.5 (Python 2.5.1 linux64 compiled mod_python.so) the changes to use Paramiko result in this exception when posting a review changelist (from Perforce) via the commandline post-review tool. HTTP POSTing to http://sw-web3.altera.com/review/api/json/accounts/login/:

Re: determine git commit sha1 id of last diff revision

Thanks for the feedback but I'm sorry I think I wasn't clear enough here. Here's the workflow post-review mybranch. --publish --revision-range a:b # review #455 diff revision 1 posted Then after getting feedback and making the appropriate changes (and you no longer remember commit revision

AD authentication w/SSPI NTLM integration

Hi all, We're running ReviewBoard 1.5 and have AD authentication working via the Python ldap module but wondered if there might be a way to authenticate the user via NTLM and Apache so they don't have to log in at all? I've installed the SSPI module for Apache 2.2 and added the relevant lines to

Re: starting review #

I would expect the Review Board log file to indicate that it's trying to fetch from the repository. That usually comes immediately after the diff parsing. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On

Re: ReviewBoard 1.5 under Apache: IOError when posting review from command line post-review tool

I'm not really sure. This is the first I've heard of this issue. The call actually comes from paramiko, a Python module we use for the SSH support. Might be worth seeing if other people outside Review Board have hit that issue. Christian On Wednesday, October 13, 2010, Rob rrom...@gmail.com

Issue 1850 in reviewboard: Add Show/Hide action to /admin/db/scmtools/repository/ page

Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 1850 by sergey.sergius: Add Show/Hide action to /admin/db/scmtools/repository/ page http://code.google.com/p/reviewboard/issues/detail?id=1850 *NOTE: If you have a patch, please submit it to

Re: Issue 1571 in reviewboard: Diff-Upload UI: Base Path field too narrow

Comment #6 on issue 1571 by gorf4673: Diff-Upload UI: Base Path field too narrow http://code.google.com/p/reviewboard/issues/detail?id=1571 Followed to this defect from Issue 1635 We have just upgraded to 1.5 the text width of the base directory and diff fields remains the same. Please

Re: Issue 1571 in reviewboard: Diff-Upload UI: Base Path field too narrow

Updates: Status: Confirmed Comment #7 on issue 1571 by trowbrds: Diff-Upload UI: Base Path field too narrow http://code.google.com/p/reviewboard/issues/detail?id=1571 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google