Re: Post-review: Review id before publishing the review request

2011-12-02 Thread Christian Hammond
I'm not entirely sure what the problem is. If your script is creating the review request, then the ID is coming back in the payload. If it's doing anything with the review request, you should have the ID. Christian -- Christian Hammond - chip...@chipx86.com Review Board -

Re: Post-review: Review id before publishing the review request

2011-12-02 Thread Nilesh Jaiswal
My script doing following steps call post-review At this point i expect the Review id get generated hence i try to fetch the review id through change number below routine call subroutine to get_review_request_by_changenum which does self.myurl = self.rbserver +

Re: Post-review: Review id before publishing the review request

2011-12-02 Thread Christian Hammond
That's happening because your script isn't logging in as the user who posted the review request. Unpublished review requests can only be accessed by the user who owns them. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. -

Re: Post-review: Review id before publishing the review request

2011-12-02 Thread Christian Hammond
The behavior hasn't changed. The way logins work has. Can you show me the code that logs in? (Btw, this is probably more appropriate for the reviewboard-dev list) Christian On Dec 2, 2011, at 5:19, jack jack jais...@gmail.com wrote: Hi Chris, Thanks for the response. My script has

Re: Error setting up subversion repository

2011-12-02 Thread Matt Billock
Additional info: - This install is on CentOS - using Apache - The ssh login is failing in paramiko. - When I attempt to save my repository info, the only error I receive is (13, 'Permission denied'). - I traced the call into paramiko's code, at sock.connect(), but cannot figure out exactly what's

Issue 2406 in reviewboard: post-review

2011-12-02 Thread reviewboard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2406 by venterpi...@gmail.com: post-review http://code.google.com/p/reviewboard/issues/detail?id=2406 When i run a post-review on a mercurial repository it gives me the following issue: Failed to execute command: ['hg',

Issue 2407 in reviewboard: Diff view issue when loading existing file diffs from mercurial

2011-12-02 Thread reviewboard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2407 by venterpi...@gmail.com: Diff view issue when loading existing file diffs from mercurial http://code.google.com/p/reviewboard/issues/detail?id=2407 This issue only seems to happen with files that is not new to the

Re: Issue 2077 in reviewboard: Incorrect git diff parsing

2011-12-02 Thread reviewboard
Comment #3 on issue 2077 by chris.a@gmail.com: Incorrect git diff parsing http://code.google.com/p/reviewboard/issues/detail?id=2077 I'm running into what appears to be the same issue here. I have a project attached to github, and it's failing to parse the diffs. It complains about

Re: Issue 2077 in reviewboard: Incorrect git diff parsing

2011-12-02 Thread reviewboard
Comment #4 on issue 2077 by chris.a@gmail.com: Incorrect git diff parsing http://code.google.com/p/reviewboard/issues/detail?id=2077 I changed that file mask to use https and it failed on a different file. I then tried setting up a clone of the repo that was on disk and has a cron

Re: Issue 2381 in reviewboard: E-mail notification does not work

2011-12-02 Thread reviewboard
Comment #6 on issue 2381 by ryan.clo...@decisionsciencescorp.com: E-mail notification does not work http://code.google.com/p/reviewboard/issues/detail?id=2381 I have tried your suggestion to change the django config and emails are still sent as root@localhost. Any other suggestions? I am

Issue 2408 in reviewboard: Cannot add comment to a comment

2011-12-02 Thread reviewboard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2408 by felixfan...@gmail.com: Cannot add comment to a comment http://code.google.com/p/reviewboard/issues/detail?id=2408 * NOTE: Do not post confidential information in this bug report. * * If you need immediate