Hi Christian, It just has the info about the file/revision that it says it can't find:
{"stat": "fail", "err": {"msg": "The file was not found in the repository", "code": 207}, "file": "webapp/zend/application/ Bootstrap.php", "revision": "89c64afda439"} If I cd to the repository dir. on the server (the RB server and mercurial repository are on the same host) and execute "hg cat -r 89c64afda439 webapp/zend/application/Bootstrap.php" I get the contents of that rev. of the file, which is definitely in the repository. And again, it's able to access that rev. of the file when I use an http:// repository path in RB. Chris On May 16, 9:12 pm, Christian Hammond <chip...@chipx86.com> wrote: > Hi Chris, > > When you do the HTTP POST and get the 400, what's the result payload like? > It should give a hint as to what's failing. At the very least, I'd expect an > error message for the path field. > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board -http://www.reviewboard.org > VMware, Inc. -http://www.vmware.com > > On Mon, May 16, 2011 at 8:59 PM, Chris Toomey > <ctdisp-reviewbo...@yahoo.com>wrote: > > > > > > > > > We're running ReviewBoard 1.5.3.1 with Mercurial and are using the "hg > > postreview" extension to post reviews to the server. This works fine > > for any repository that we've entered via the RB admin UI with a path > > (URI) starting with http://, but the RB server replies with a 400 > > response reporting a 207 error (file not found in the repository) when > > we try to configure the same repository to have a ssh:// path. We > > want to use ssh:// and not http:// URIs for select repositories for > > access-control reasons, but to do an apples to apples comparison I > > wanted to try ssh:// for a repository that is known to work via http://. > > > The server reports 201 on the POST /rb/api/review-requests/ call, 200 > > on the PUT /rb/api/review-requests/489/draft/, but 400 on the POST /rb/ > > api/review-requests/489/diffs/ call. > > > The submitted diff is the same in the call that fails when using an ssh:// > > repository URI and the one that succeeds with a http:// repository > > API. > > > I've verified that the ssh authentication works -- the sshrepo > > validate_repo call succeeds, and there are no errors logged to /var/ > > log/auth.log. > > > I've set DEBUG = True in my settings yet the reviewboard log doesn't > > log anything about this issue. > > > Any ideas on why this might be failing, and how to debug it further > > (where to add additional logging or where to set breakpoints, etc.)? > > > thanks, > > Chris > > > -- > > 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