Awesome! thank you Christian

On Monday, July 3, 2017 at 4:35:24 PM UTC+10, Christian Hammond wrote:
>
> I don't know that that will solve it, and suspect that's not the cause. 
> Unfortunately I won't have any time for community support the next few 
> days, but I'll see if someone else can follow up with you on debugging 
> steps.
>
> Christian
>
>
> On Sun, Jul 2, 2017 at 22:41 MoonWalker <[email protected] 
> <javascript:>> wrote:
>
>> Christian,
>>
>> Shall I update Gitlab to 9.3?
>>
>>
>> On Friday, June 30, 2017 at 3:07:23 PM UTC+10, MoonWalker wrote:
>>>
>>> Hi Christian,
>>>
>>> We use GitLab Community Edition 8.13.2. RB has access to about 60 repos 
>>> and around 10 have a dash on their names. Not sure how many repos gitlab 
>>> has in total
>>>
>>> On Friday, June 30, 2017 at 12:03:32 PM UTC+10, Christian Hammond wrote:
>>>>
>>>> Hey,
>>>>
>>>> What version of GitLab are you using, and roughly how many repositories 
>>>> are there?
>>>>
>>>> There's a few reasons why this may happen:
>>>>
>>>> 1) The repository name might not actually officially have a "-" in it, 
>>>> in terms of the name returned in the API. We scan through the list of 
>>>> repositories, trying to find the one you specified, and if we can't, we 
>>>> show that error.
>>>>
>>>> 2) Due to completely broken GitLab API pagination in this resource when 
>>>> we implemented this, it may not be able to find the repository if you have 
>>>> more than 100 repositories owned by this user or group. (We need to check 
>>>> if they've fixed the API and then ship fixed support on our end.)
>>>>
>>>> I'd guess #2, if you have a lot of repositories.
>>>>
>>>> Christian
>>>>
>>>> On Thu, Jun 29, 2017 at 5:19 PM, MoonWalker <[email protected]> 
>>>> wrote:
>>>>
>>>>> Not sure if this issue is present only on the latest RB 2.5.13.1 or 
>>>>> not. I had to to update the BUG tracker information on each repository 
>>>>> and 
>>>>> I the system keep sending me the same error message A repository with 
>>>>> this name was not found on this group, or your user may not have access 
>>>>> to 
>>>>> it. I noticed that that this only happens with the repositories that 
>>>>> have a '-" on the repository name (my-repo-monkey). I am using the same 
>>>>> credentials for the other repos and everything is okay.
>>>>>
>>>>> -- 
>>>>> Supercharge your Review Board with Power Pack: 
>>>>> https://www.reviewboard.org/powerpack/
>>>>> Want us to host Review Board for you? Check out RBCommons: 
>>>>> https://rbcommons.com/
>>>>> Happy user? Let us know! https://www.reviewboard.org/users/
>>>>> --- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "reviewboard" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to [email protected].
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>>
>>>>
>>>> -- 
>>>> Christian Hammond
>>>> President/CEO of Beanbag <https://www.beanbaginc.com/>
>>>> Makers of Review Board <https://www.reviewboard.org/>
>>>>
>>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> -- 
> Christian Hammond
> President/CEO of Beanbag
> Makers of Review Board
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to