After reading this discussion, I had filed a bug in March to track this 
issue.

http://code.google.com/p/reviewboard/issues/detail?id=2558

Thanks,
Ivan

On Monday, March 19, 2012 3:27:54 PM UTC-7, Christian Hammond wrote:
>
> Ohh, interesting. Yeah, definitely a bug there.
>
> What type of repository is this?
>
> Christian
>
> -- 
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Mon, Mar 19, 2012 at 3:17 PM, heffe <ghe...@gmail.com> wrote:
>
>> That's the problem.  "jimmy" is not authorized to access the repository 
>> where post-review is running into the error.  The review being created by 
>> post-review is *not *against the repository that is invitation-only.  It 
>> is against another repository in the list that post-review hasn't gotten to 
>> yet.  The question is, if post-review iterates through the repository list 
>> on behalf of user "jimmy", but runs across a repository where it can't get 
>> the data because of permissions, and hasn't yet reached the one that is 
>> appropriate for the sandbox, does it just fail as I am seeing?
>>
>> Example list of repos that post-review iterates over to find out where to 
>> submit the request:
>> [repo1] - public
>> [repo2] - public
>> [repo3] - invitation-only
>> [repo4] - public, the one where "jimmy" intends to submit the review 
>> request.
>>
>>
>> Thanks,
>> Jeff
>>
>> -- 
>> 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
>>
>
>
On Monday, March 19, 2012 3:27:54 PM UTC-7, Christian Hammond wrote:
>
> Ohh, interesting. Yeah, definitely a bug there.
>
> What type of repository is this?
>
> Christian
>
> -- 
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Mon, Mar 19, 2012 at 3:17 PM, heffe <ghe...@gmail.com> wrote:
>
>> That's the problem.  "jimmy" is not authorized to access the repository 
>> where post-review is running into the error.  The review being created by 
>> post-review is *not *against the repository that is invitation-only.  It 
>> is against another repository in the list that post-review hasn't gotten to 
>> yet.  The question is, if post-review iterates through the repository list 
>> on behalf of user "jimmy", but runs across a repository where it can't get 
>> the data because of permissions, and hasn't yet reached the one that is 
>> appropriate for the sandbox, does it just fail as I am seeing?
>>
>> Example list of repos that post-review iterates over to find out where to 
>> submit the request:
>> [repo1] - public
>> [repo2] - public
>> [repo3] - invitation-only
>> [repo4] - public, the one where "jimmy" intends to submit the review 
>> request.
>>
>>
>> Thanks,
>> Jeff
>>
>> -- 
>> 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
>>
>
>
On Monday, March 19, 2012 3:27:54 PM UTC-7, Christian Hammond wrote:
>
> Ohh, interesting. Yeah, definitely a bug there.
>
> What type of repository is this?
>
> Christian
>
> -- 
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Mon, Mar 19, 2012 at 3:17 PM, heffe <ghe...@gmail.com> wrote:
>
>> That's the problem.  "jimmy" is not authorized to access the repository 
>> where post-review is running into the error.  The review being created by 
>> post-review is *not *against the repository that is invitation-only.  It 
>> is against another repository in the list that post-review hasn't gotten to 
>> yet.  The question is, if post-review iterates through the repository list 
>> on behalf of user "jimmy", but runs across a repository where it can't get 
>> the data because of permissions, and hasn't yet reached the one that is 
>> appropriate for the sandbox, does it just fail as I am seeing?
>>
>> Example list of repos that post-review iterates over to find out where to 
>> submit the request:
>> [repo1] - public
>> [repo2] - public
>> [repo3] - invitation-only
>> [repo4] - public, the one where "jimmy" intends to submit the review 
>> request.
>>
>>
>> Thanks,
>> Jeff
>>
>> -- 
>> 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
>>
>
>

-- 
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

Reply via email to