On Friday 11 February 2011 10:07:35 pm Jerry wrote:
> And, the dbug log from RBTools' post-review:
>
> -
> $ post-review --debug
>
> >>> RBTools 0.3.2
> >>> Home = C:\Documents and Settings\jm\Application Data
> >>> hg showconfig
> >>> hg root
> >>> hg svn info
> >>> Using candidate path 'defau
On Friday 11 February 2011 11:22:47 pm Jerry wrote:
> The relevant lines from reviewboard.log on the server:
> -
> 2011-02-11 14:09:25,121 - DEBUG - Trying discovered key
> 287637e1d8a393fefcc82e2c35f4f567 in /var/www/reviewboard/data/.ssh/
> id_dsa
> 2011-02-11 14:09:25,156 - DEBUG - userauth
> Are you using a fully-qualified domain for the path, or just "scm" or
something? It may matter.
I was just using scm. I just put in the fully-qualified path and will
try again (see below.).
> Also, try cloning the repository using that path on your server, just to see
what happens.
I am able t
Are you using a fully-qualified domain for the path, or just "scm" or
something? It may matter.
Also, try cloning the repository using that path on your server, just to see
what happens.
I assume you have an SSH key uploaded. Can you verify it's the right one in
the Admin UI?
Christian
--
Chri
ReviewBoard version 1.5.3.
I notice that for the review requests created by RBTools post-review,
if I go to the web UI and try to select the review request, I also get
a 500 error in my browser.
OK, so here is the full output in reviewboard.log for a post-review
command:
-
2011-02-11 13:38:38
A 500. Interesting... So it's more than just a matter of not finding the
right path in the repository.
What version of Review Board is this?
Can you enable logging on the Review Board end, repeat the process, and then
find the accompanying error for this in the reviewboard.log file?
Christian
-
And, the dbug log from RBTools' post-review:
-
$ post-review --debug
>>> RBTools 0.3.2
>>> Home = C:\Documents and Settings\jm\Application Data
>>> hg showconfig
>>> hg root
>>> hg svn info
>>> Using candidate path 'default':
>>> 'ssh://scm//opt/hg/main/core/AnyModalConsole'
>>> repository in
Thanks, Christian. I had tried hg postreview from mdelagra's fork
(https://bitbucket.org/mdelagra/mercurial-reviewboard) first, and was
unsuccessful, so I went to the GUI to try to eliminate that as a
culprit. Is this the tool you are referring to?
Here is the --debug result from that (I added s
Hi Jerry,
Have you tried post-review or hg post-review? Can you try these (with debug
mode on, which is --debug on post-review at least, dunno about hg
post-review) and see if you still hit this problem? If so, the debug log
would be helpful in identifying the problem.
Christian
--
Christian Ha
