date:20151216

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

2015-12-16 Thread Christian Hammond

That certainly shouldn't be necessary. Sounds like maybe there was a bad
package?

If it ever happens again, please let me know. I want to be sure we figure
out what's causing that.

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Wed, Dec 16, 2015 at 5:57 AM, Cian Mc Govern 
wrote:

> On 15 December 2015 at 19:15, Christian Hammond 
> wrote:
>
>> Hi,
>>
>> collectstatic isn't meant to be run by end users. It's intended only for
>> the packaging steps, and running it manually can cause problems. I want to
>> better understand the need to run this command, though. Can you go into
>> this a bit more?
>>
>> Christian
>>
>> --
>> Christian Hammond - chip...@chipx86.com
>> Review Board - https://www.reviewboard.org
>> Beanbag, Inc. - https://www.beanbaginc.com
>>
>
> It fixed some upgrade issues I encountered with previous versions so I run
> it as part of my upgrade process for every version. I'll stop doing it if
> it can cause issues though.
>
>
>> On Tue, Dec 15, 2015 at 1:09 AM, Cian Mc Govern 
>> wrote:
>>
>>> On 4 December 2015 at 16:18, Stephen Gallagher <
>>> step...@gallagherhome.com> wrote:
>>>
 Hello, folks! It's time for a big update. As many of you are probably
 aware, I maintain the RPMs of Review Board that live in Fedora's EPEL
 project[1] (Extra Packages for Enterprise Linux).

>>>
>>> Thanks for your work on this Stephen. No complaints from me, both a
>>> clean install and an upgrade worked without issue.
>>>
>>> One thing I noticed was that the ReviewBoard package doesn't require
>>> uglify-js which is required when running 'rb-site manage /path/to/site
>>> collectstatic'. It might be worth adding that in a future release, I
>>> believe it's only a build dependency at the moment.
>>>
>>> --
>>> 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 reviewboard+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> 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 reviewboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Suddenly getting a Error data : A repository was not found at the specified path.

2015-12-16 Thread Christian Hammond

Hi,

How is the repository specified in the admin UI? Is it based on some IP
address or hostname that may not be resolving anymore?

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Wed, Dec 16, 2015 at 11:17 AM, Luc Ferland  wrote:

> Hi all,
>
> We have 3 reviewboard serveur here, all with perforce. One of them
> suddenly stopped working. When we try to submit a review we get the
> following error :
>
> RepositoryNotFoundError: A repository was not found at the specified path.
>
>
>
>
> Don't really what has changed. Rebooted the server. The web console is
> accessible.
>
> I searched the forum but it seemed that most often it is related to
> selinux, which is not enable on this machine.
>
> I'am a bit out of ideas, here is the exact log error on the reviewboard
> log :
>
> - Error running should_render for ReviewRequestFieldset  'reviewboard.reviews.builtin_fields.ChangeField'>: A repository was not found 
> at the specified path.
> Traceback (most recent call last):
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/reviews/templatetags/reviewtags.py",
>  line 303, in for_review_request_field
> s.append(nodelist.render(context))
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
>  line 840, in render
> bit = self.render_node(node, context)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
>  line 854, in render_node
> return node.render(context)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
>  line 891, in render
> output = self.filter_expression.resolve(context)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
>  line 585, in resolve
> obj = self.var.resolve(context)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
>  line 735, in resolve
> value = self._resolve_lookup(context)
>   File 
> "/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
>  line 789, in _resolve_lookup
> current = current()
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/reviews/fields.py",
>  line 337, in as_html
> return self.render_value(self.value)
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/reviews/builtin_fields.py",
>  line 394, in render_value
> is_pending, changenum = review_request.changeset_is_pending(changenum)
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/reviews/models/review_request.py",
>  line 536, in changeset_is_pending
> changeset = scmtool.get_changeset(commit_id, allow_empty=True)
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/scmtools/perforce.py",
>  line 316, in get_changeset
> changeset = self.client.get_changeset(changesetid)
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/scmtools/perforce.py",
>  line 206, in get_changeset
> return self._run_worker(lambda: self._get_changeset(changesetid))
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/scmtools/perforce.py",
>  line 187, in _run_worker
> self._convert_p4exception_to_scmexception(e)
>   File 
> "/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/scmtools/perforce.py",
>  line 173, in _convert_p4exception_to_scmexception
> raise RepositoryNotFoundError
> RepositoryNotFoundError: A repository was not found at the specified path.
>
> --
> 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 reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitLab hosting stopped working

2015-12-16 Thread Christian Hammond

Hi Ian,

Sounds like that auth token may have also been removed. We don't really
have a good way of resetting these for GitLab right now in Review Board.
There's a workaround, but it's not ideal, and we're wanting to build
something nicer for this:

1) Go into the Review Board admin UI -> Database -> Hosting Accounts.
2) Edit the entry for your GitLab account, and temporarily rename the
username.
3) Add a new repository and link your account again. This will be
temporary. You don't even need to specify a valid repository name, since we
don't care if that's created. We just care that the linking process worked.
4) Go back into the Hosting Accounts section, and find the new account.
Copy all the authentication data (it's a JSON payload), and paste it into
the original account.
5) Delete the new one and rename the original one back.

This will basically update the existing linked account, in a round-about
way. In future versions, we'll have a nicer process in place for this (we
have a lot of work in progress for a better repository management
experience).

Let me know if that works!

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Tue, Dec 15, 2015 at 9:00 PM, Ian  wrote:

> Yeah I just double checked via GitLab's web UI.  The password for the
> shared account has changed since I originally set up the repositories.  I
> tried the "link new account" option and typed in the current username and
> password but it doesn't want to work for some reason.  Our GitLab
> installation has been upgraded a few times too, it's GitLab Enterprise
> Edition 7.14.3-ee 60aabef if that matters.
>
> Ian
>
> On Monday, December 7, 2015 at 1:53:02 AM UTC-8, Christian Hammond wrote:
>>
>> Hi Ian,
>>
>> Can you verify that the username associated with those repositories still
>> has the necessary access permissions on the GitLab server?
>>
>> I checked the code in question, involving repository verification and how
>> credentials are used, and it hasn't changed since 2.0.x, so at this point
>> I'd want to verify the GitLab setup.
>>
>> Christian
>>
>> --
>> Christian Hammond - chri...@beanbaginc.com
>> Review Board - https://www.reviewboard.org
>> Beanbag, Inc. - https://www.beanbaginc.com
>>
>> On Sun, Dec 6, 2015 at 3:11 PM, Ian  wrote:
>>
>>> Any idea on how I could fix this?
>>>
>>> Ian
>>>
>>>
>>> On Tuesday, November 17, 2015 at 4:56:19 PM UTC-8, Ian wrote:

 Yes, existing review requests against the repository are loading, I
 just can't change the repository configuration.

 Ian

 On Monday, November 16, 2015 at 11:30:51 PM UTC-8, Christian Hammond
 wrote:
>
> Hi Ian,
>
> Do existing review requests against this repository still work? Is
> this solely when changing the repository configuration?
>
> Christian
>
> --
> Christian Hammond - chri...@beanbaginc.com
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>
> On Mon, Nov 16, 2015 at 7:47 PM, Ian  wrote:
>
>> I recently updated to ReviewBoard 2.5.1 and now I can't change any of
>> my GitLab repositories, when I do it says "A repository with this name 
>> was
>> not found on this group, or your user may not have access to it."  I
>> verified that I can log into my GitLab installation and see the
>> repositories from a web browser running on the ReviewBoard server using 
>> the
>> same account.  I don't suppose this is a known issue?  My config looks 
>> like
>> this.
>>
>> Hosting Service: GitLab
>> Service URL: https://gitlab.domain.com
>> Account: username
>> Repository Type: Git
>> Repository Plan: Group
>> GitLab Group Name: groupname
>> Repository Name: repositoryname
>>
>> Ian
>>
>> --
>> 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 reviewboard...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>
> --
>>> 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
>>>

Suddenly getting a Error data : A repository was not found at the specified path.

2015-12-16 Thread Luc Ferland

Hi all,

We have 3 reviewboard serveur here, all with perforce. One of them suddenly 
stopped working. When we try to submit a review we get the following error :

RepositoryNotFoundError: A repository was not found at the specified path.




Don't really what has changed. Rebooted the server. The web console is 
accessible.

I searched the forum but it seemed that most often it is related to 
selinux, which is not enable on this machine.

I'am a bit out of ideas, here is the exact log error on the reviewboard log 
: 

- Error running should_render for ReviewRequestFieldset : A repository was not found 
at the specified path.
Traceback (most recent call last):
  File 
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/reviews/templatetags/reviewtags.py",
 line 303, in for_review_request_field
s.append(nodelist.render(context))
  File 
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
 line 840, in render
bit = self.render_node(node, context)
  File 
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
 line 854, in render_node
return node.render(context)
  File 
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
 line 891, in render
output = self.filter_expression.resolve(context)
  File 
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
 line 585, in resolve
obj = self.var.resolve(context)
  File 
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
 line 735, in resolve
value = self._resolve_lookup(context)
  File 
"/usr/local/lib/python2.7/dist-packages/Django-1.6.11-py2.7.egg/django/template/base.py",
 line 789, in _resolve_lookup
current = current()
  File 
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/reviews/fields.py",
 line 337, in as_html
return self.render_value(self.value)
  File 
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/reviews/builtin_fields.py",
 line 394, in render_value
is_pending, changenum = review_request.changeset_is_pending(changenum)
  File 
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/reviews/models/review_request.py",
 line 536, in changeset_is_pending
changeset = scmtool.get_changeset(commit_id, allow_empty=True)
  File 
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/scmtools/perforce.py",
 line 316, in get_changeset
changeset = self.client.get_changeset(changesetid)
  File 
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/scmtools/perforce.py",
 line 206, in get_changeset
return self._run_worker(lambda: self._get_changeset(changesetid))
  File 
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/scmtools/perforce.py",
 line 187, in _run_worker
self._convert_p4exception_to_scmexception(e)
  File 
"/usr/local/lib/python2.7/dist-packages/ReviewBoard-2.0.20-py2.7.egg/reviewboard/scmtools/perforce.py",
 line 173, in _convert_p4exception_to_scmexception
raise RepositoryNotFoundError
RepositoryNotFoundError: A repository was not found at the specified path.

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitLab hosting stopped working

2015-12-16 Thread Christian Hammond

Hi Ian,

There's a few possible APIs that it may call, but I realized what could
potentially be the issue...

How many repositories do you have on the server? Due to limitations that
used to exist (hopefully don't anymore) with the GitLab API, we weren't
able to fetch more than 100 entries very cleanly, and our code is still
adhering to that limitation.

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Wed, Dec 16, 2015 at 6:46 PM, Ian  wrote:

> It worked far enough to re-link, I got a new private_token for the new
> temporary hosting account.  But I still get the same error every time I try
> to save any of my repositories.  Is there a particular URL that Review
> Board builds based on the repository information I entered that I could
> test in a web browser?
>
> Ian
>
> On Wednesday, December 16, 2015 at 12:00:54 PM UTC-8, Christian Hammond
> wrote:
>>
>> Hi Ian,
>>
>> Sounds like that auth token may have also been removed. We don't really
>> have a good way of resetting these for GitLab right now in Review Board.
>> There's a workaround, but it's not ideal, and we're wanting to build
>> something nicer for this:
>>
>> 1) Go into the Review Board admin UI -> Database -> Hosting Accounts.
>> 2) Edit the entry for your GitLab account, and temporarily rename the
>> username.
>> 3) Add a new repository and link your account again. This will be
>> temporary. You don't even need to specify a valid repository name, since we
>> don't care if that's created. We just care that the linking process worked.
>> 4) Go back into the Hosting Accounts section, and find the new account.
>> Copy all the authentication data (it's a JSON payload), and paste it into
>> the original account.
>> 5) Delete the new one and rename the original one back.
>>
>> This will basically update the existing linked account, in a round-about
>> way. In future versions, we'll have a nicer process in place for this (we
>> have a lot of work in progress for a better repository management
>> experience).
>>
>> Let me know if that works!
>>
>> Christian
>>
>> --
>> Christian Hammond - chri...@beanbaginc.com
>> Review Board - https://www.reviewboard.org
>> Beanbag, Inc. - https://www.beanbaginc.com
>>
>> On Tue, Dec 15, 2015 at 9:00 PM, Ian  wrote:
>>
>>> Yeah I just double checked via GitLab's web UI.  The password for the
>>> shared account has changed since I originally set up the repositories.  I
>>> tried the "link new account" option and typed in the current username and
>>> password but it doesn't want to work for some reason.  Our GitLab
>>> installation has been upgraded a few times too, it's GitLab Enterprise
>>> Edition 7.14.3-ee 60aabef if that matters.
>>>
>>> Ian
>>>
>>> On Monday, December 7, 2015 at 1:53:02 AM UTC-8, Christian Hammond wrote:

 Hi Ian,

 Can you verify that the username associated with those repositories
 still has the necessary access permissions on the GitLab server?

 I checked the code in question, involving repository verification and
 how credentials are used, and it hasn't changed since 2.0.x, so at this
 point I'd want to verify the GitLab setup.

 Christian

 --
 Christian Hammond - chri...@beanbaginc.com
 Review Board - https://www.reviewboard.org
 Beanbag, Inc. - https://www.beanbaginc.com

 On Sun, Dec 6, 2015 at 3:11 PM, Ian  wrote:

> Any idea on how I could fix this?
>
> Ian
>
>
> On Tuesday, November 17, 2015 at 4:56:19 PM UTC-8, Ian wrote:
>>
>> Yes, existing review requests against the repository are loading, I
>> just can't change the repository configuration.
>>
>> Ian
>>
>> On Monday, November 16, 2015 at 11:30:51 PM UTC-8, Christian Hammond
>> wrote:
>>>
>>> Hi Ian,
>>>
>>> Do existing review requests against this repository still work? Is
>>> this solely when changing the repository configuration?
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - chri...@beanbaginc.com
>>> Review Board - https://www.reviewboard.org
>>> Beanbag, Inc. - https://www.beanbaginc.com
>>>
>>> On Mon, Nov 16, 2015 at 7:47 PM, Ian  wrote:
>>>
 I recently updated to ReviewBoard 2.5.1 and now I can't change any
 of my GitLab repositories, when I do it says "A repository with this 
 name
 was not found on this group, or your user may not have access to it."  
 I
 verified that I can log into my GitLab installation and see the
 repositories from a web browser running on the ReviewBoard server 
 using the
 same account.  I don't suppose this is a known issue?  My config looks 
 like
 this.

 Hosting Service: GitLab
 Service URL:

Re: GitLab hosting stopped working

2015-12-16 Thread Ian

It worked far enough to re-link, I got a new private_token for the new 
temporary hosting account.  But I still get the same error every time I try 
to save any of my repositories.  Is there a particular URL that Review 
Board builds based on the repository information I entered that I could 
test in a web browser?

Ian

On Wednesday, December 16, 2015 at 12:00:54 PM UTC-8, Christian Hammond 
wrote:
>
> Hi Ian,
>
> Sounds like that auth token may have also been removed. We don't really 
> have a good way of resetting these for GitLab right now in Review Board. 
> There's a workaround, but it's not ideal, and we're wanting to build 
> something nicer for this:
>
> 1) Go into the Review Board admin UI -> Database -> Hosting Accounts.
> 2) Edit the entry for your GitLab account, and temporarily rename the 
> username.
> 3) Add a new repository and link your account again. This will be 
> temporary. You don't even need to specify a valid repository name, since we 
> don't care if that's created. We just care that the linking process worked.
> 4) Go back into the Hosting Accounts section, and find the new account. 
> Copy all the authentication data (it's a JSON payload), and paste it into 
> the original account.
> 5) Delete the new one and rename the original one back.
>
> This will basically update the existing linked account, in a round-about 
> way. In future versions, we'll have a nicer process in place for this (we 
> have a lot of work in progress for a better repository management 
> experience).
>
> Let me know if that works!
>
> Christian
>
> -- 
> Christian Hammond - chri...@beanbaginc.com 
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>
> On Tue, Dec 15, 2015 at 9:00 PM, Ian  
> wrote:
>
>> Yeah I just double checked via GitLab's web UI.  The password for the 
>> shared account has changed since I originally set up the repositories.  I 
>> tried the "link new account" option and typed in the current username and 
>> password but it doesn't want to work for some reason.  Our GitLab 
>> installation has been upgraded a few times too, it's GitLab Enterprise 
>> Edition 7.14.3-ee 60aabef if that matters.
>>
>> Ian
>>
>> On Monday, December 7, 2015 at 1:53:02 AM UTC-8, Christian Hammond wrote:
>>>
>>> Hi Ian,
>>>
>>> Can you verify that the username associated with those repositories 
>>> still has the necessary access permissions on the GitLab server?
>>>
>>> I checked the code in question, involving repository verification and 
>>> how credentials are used, and it hasn't changed since 2.0.x, so at this 
>>> point I'd want to verify the GitLab setup.
>>>
>>> Christian
>>>
>>> -- 
>>> Christian Hammond - chri...@beanbaginc.com
>>> Review Board - https://www.reviewboard.org
>>> Beanbag, Inc. - https://www.beanbaginc.com
>>>
>>> On Sun, Dec 6, 2015 at 3:11 PM, Ian  wrote:
>>>
 Any idea on how I could fix this?

 Ian


 On Tuesday, November 17, 2015 at 4:56:19 PM UTC-8, Ian wrote:
>
> Yes, existing review requests against the repository are loading, I 
> just can't change the repository configuration.
>
> Ian
>
> On Monday, November 16, 2015 at 11:30:51 PM UTC-8, Christian Hammond 
> wrote:
>>
>> Hi Ian,
>>
>> Do existing review requests against this repository still work? Is 
>> this solely when changing the repository configuration?
>>
>> Christian
>>
>> -- 
>> Christian Hammond - chri...@beanbaginc.com
>> Review Board - https://www.reviewboard.org
>> Beanbag, Inc. - https://www.beanbaginc.com
>>
>> On Mon, Nov 16, 2015 at 7:47 PM, Ian  wrote:
>>
>>> I recently updated to ReviewBoard 2.5.1 and now I can't change any 
>>> of my GitLab repositories, when I do it says "A repository with this 
>>> name 
>>> was not found on this group, or your user may not have access to it."  
>>> I 
>>> verified that I can log into my GitLab installation and see the 
>>> repositories from a web browser running on the ReviewBoard server using 
>>> the 
>>> same account.  I don't suppose this is a known issue?  My config looks 
>>> like 
>>> this.
>>>
>>> Hosting Service: GitLab
>>> Service URL: https://gitlab.domain.com
>>> Account: username
>>> Repository Type: Git
>>> Repository Plan: Group
>>> GitLab Group Name: groupname
>>> Repository Name: repositoryname
>>>
>>> Ian
>>>
>>> -- 
>>> 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

Re: GitLab hosting stopped working

2015-12-16 Thread Christian Hammond

Okay, this is likely the issue. The repositories can't be found because we
couldn't sanely iterate before, and had to limit it to 100 repositories.

A workaround (not a great one) is to have a user per 100 repositories, so
that the pagination issue doesn't happen.

Another is to temporarily modify the check_repository method in
reviewboard/hostingsvcs/gitlab.py to return early, instead of attempting to
look up the repository, so that you can save.

I'll see what we can do for the next releases of Review Board.

Christian

-- 
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com

On Wed, Dec 16, 2015 at 11:51 PM, Ian  wrote:

> How many repositories total?  Probably way (way) more than 100.  But I
> only have about 10 configured in Review Board.
>
> Ian
>
> On Wednesday, December 16, 2015 at 11:18:18 PM UTC-8, Christian Hammond
> wrote:
>>
>> Hi Ian,
>>
>> There's a few possible APIs that it may call, but I realized what could
>> potentially be the issue...
>>
>> How many repositories do you have on the server? Due to limitations that
>> used to exist (hopefully don't anymore) with the GitLab API, we weren't
>> able to fetch more than 100 entries very cleanly, and our code is still
>> adhering to that limitation.
>>
>> Christian
>>
>> --
>> Christian Hammond - chri...@beanbaginc.com
>> Review Board - https://www.reviewboard.org
>> Beanbag, Inc. - https://www.beanbaginc.com
>>
>> On Wed, Dec 16, 2015 at 6:46 PM, Ian  wrote:
>>
>>> It worked far enough to re-link, I got a new private_token for the new
>>> temporary hosting account.  But I still get the same error every time I try
>>> to save any of my repositories.  Is there a particular URL that Review
>>> Board builds based on the repository information I entered that I could
>>> test in a web browser?
>>>
>>> Ian
>>>
>>> On Wednesday, December 16, 2015 at 12:00:54 PM UTC-8, Christian Hammond
>>> wrote:

 Hi Ian,

 Sounds like that auth token may have also been removed. We don't really
 have a good way of resetting these for GitLab right now in Review Board.
 There's a workaround, but it's not ideal, and we're wanting to build
 something nicer for this:

 1) Go into the Review Board admin UI -> Database -> Hosting Accounts.
 2) Edit the entry for your GitLab account, and temporarily rename the
 username.
 3) Add a new repository and link your account again. This will be
 temporary. You don't even need to specify a valid repository name, since we
 don't care if that's created. We just care that the linking process worked.
 4) Go back into the Hosting Accounts section, and find the new account.
 Copy all the authentication data (it's a JSON payload), and paste it into
 the original account.
 5) Delete the new one and rename the original one back.

 This will basically update the existing linked account, in a
 round-about way. In future versions, we'll have a nicer process in place
 for this (we have a lot of work in progress for a better repository
 management experience).

 Let me know if that works!

 Christian

 --
 Christian Hammond - chri...@beanbaginc.com
 Review Board - https://www.reviewboard.org
 Beanbag, Inc. - https://www.beanbaginc.com

 On Tue, Dec 15, 2015 at 9:00 PM, Ian  wrote:

> Yeah I just double checked via GitLab's web UI.  The password for the
> shared account has changed since I originally set up the repositories.  I
> tried the "link new account" option and typed in the current username and
> password but it doesn't want to work for some reason.  Our GitLab
> installation has been upgraded a few times too, it's GitLab Enterprise
> Edition 7.14.3-ee 60aabef if that matters.
>
> Ian
>
> On Monday, December 7, 2015 at 1:53:02 AM UTC-8, Christian Hammond
> wrote:
>>
>> Hi Ian,
>>
>> Can you verify that the username associated with those repositories
>> still has the necessary access permissions on the GitLab server?
>>
>> I checked the code in question, involving repository verification and
>> how credentials are used, and it hasn't changed since 2.0.x, so at this
>> point I'd want to verify the GitLab setup.
>>
>> Christian
>>
>> --
>> Christian Hammond - chri...@beanbaginc.com
>> Review Board - https://www.reviewboard.org
>> Beanbag, Inc. - https://www.beanbaginc.com
>>
>> On Sun, Dec 6, 2015 at 3:11 PM, Ian  wrote:
>>
>>> Any idea on how I could fix this?
>>>
>>> Ian
>>>
>>>
>>> On Tuesday, November 17, 2015 at 4:56:19 PM UTC-8, Ian wrote:

 Yes, existing review requests against the repository are loading, I
 just can't change the repository configuration.

 Ian

Re: GitLab hosting stopped working

2015-12-16 Thread Ian

How many repositories total?  Probably way (way) more than 100.  But I only 
have about 10 configured in Review Board.

Ian

On Wednesday, December 16, 2015 at 11:18:18 PM UTC-8, Christian Hammond 
wrote:
>
> Hi Ian,
>
> There's a few possible APIs that it may call, but I realized what could 
> potentially be the issue...
>
> How many repositories do you have on the server? Due to limitations that 
> used to exist (hopefully don't anymore) with the GitLab API, we weren't 
> able to fetch more than 100 entries very cleanly, and our code is still 
> adhering to that limitation.
>
> Christian
>
> -- 
> Christian Hammond - chri...@beanbaginc.com 
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>
> On Wed, Dec 16, 2015 at 6:46 PM, Ian  
> wrote:
>
>> It worked far enough to re-link, I got a new private_token for the new 
>> temporary hosting account.  But I still get the same error every time I try 
>> to save any of my repositories.  Is there a particular URL that Review 
>> Board builds based on the repository information I entered that I could 
>> test in a web browser?
>>
>> Ian
>>
>> On Wednesday, December 16, 2015 at 12:00:54 PM UTC-8, Christian Hammond 
>> wrote:
>>>
>>> Hi Ian,
>>>
>>> Sounds like that auth token may have also been removed. We don't really 
>>> have a good way of resetting these for GitLab right now in Review Board. 
>>> There's a workaround, but it's not ideal, and we're wanting to build 
>>> something nicer for this:
>>>
>>> 1) Go into the Review Board admin UI -> Database -> Hosting Accounts.
>>> 2) Edit the entry for your GitLab account, and temporarily rename the 
>>> username.
>>> 3) Add a new repository and link your account again. This will be 
>>> temporary. You don't even need to specify a valid repository name, since we 
>>> don't care if that's created. We just care that the linking process worked.
>>> 4) Go back into the Hosting Accounts section, and find the new account. 
>>> Copy all the authentication data (it's a JSON payload), and paste it into 
>>> the original account.
>>> 5) Delete the new one and rename the original one back.
>>>
>>> This will basically update the existing linked account, in a round-about 
>>> way. In future versions, we'll have a nicer process in place for this (we 
>>> have a lot of work in progress for a better repository management 
>>> experience).
>>>
>>> Let me know if that works!
>>>
>>> Christian
>>>
>>> -- 
>>> Christian Hammond - chri...@beanbaginc.com
>>> Review Board - https://www.reviewboard.org
>>> Beanbag, Inc. - https://www.beanbaginc.com
>>>
>>> On Tue, Dec 15, 2015 at 9:00 PM, Ian  wrote:
>>>
 Yeah I just double checked via GitLab's web UI.  The password for the 
 shared account has changed since I originally set up the repositories.  I 
 tried the "link new account" option and typed in the current username and 
 password but it doesn't want to work for some reason.  Our GitLab 
 installation has been upgraded a few times too, it's GitLab Enterprise 
 Edition 7.14.3-ee 60aabef if that matters.

 Ian

 On Monday, December 7, 2015 at 1:53:02 AM UTC-8, Christian Hammond 
 wrote:
>
> Hi Ian,
>
> Can you verify that the username associated with those repositories 
> still has the necessary access permissions on the GitLab server?
>
> I checked the code in question, involving repository verification and 
> how credentials are used, and it hasn't changed since 2.0.x, so at this 
> point I'd want to verify the GitLab setup.
>
> Christian
>
> -- 
> Christian Hammond - chri...@beanbaginc.com
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>
> On Sun, Dec 6, 2015 at 3:11 PM, Ian  wrote:
>
>> Any idea on how I could fix this?
>>
>> Ian
>>
>>
>> On Tuesday, November 17, 2015 at 4:56:19 PM UTC-8, Ian wrote:
>>>
>>> Yes, existing review requests against the repository are loading, I 
>>> just can't change the repository configuration.
>>>
>>> Ian
>>>
>>> On Monday, November 16, 2015 at 11:30:51 PM UTC-8, Christian Hammond 
>>> wrote:

 Hi Ian,

 Do existing review requests against this repository still work? Is 
 this solely when changing the repository configuration?

 Christian

 -- 
 Christian Hammond - chri...@beanbaginc.com
 Review Board - https://www.reviewboard.org
 Beanbag, Inc. - https://www.beanbaginc.com

 On Mon, Nov 16, 2015 at 7:47 PM, Ian  wrote:

> I recently updated to ReviewBoard 2.5.1 and now I can't change any 
> of my GitLab repositories, when I do it says "A repository with this 
> name 
> was not found on this group, or your user may not have

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

2015-12-16 Thread Cian Mc Govern

On 15 December 2015 at 19:15, Christian Hammond  wrote:

> Hi,
>
> collectstatic isn't meant to be run by end users. It's intended only for
> the packaging steps, and running it manually can cause problems. I want to
> better understand the need to run this command, though. Can you go into
> this a bit more?
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
>

It fixed some upgrade issues I encountered with previous versions so I run
it as part of my upgrade process for every version. I'll stop doing it if
it can cause issues though.


> On Tue, Dec 15, 2015 at 1:09 AM, Cian Mc Govern 
> wrote:
>
>> On 4 December 2015 at 16:18, Stephen Gallagher > > wrote:
>>
>>> Hello, folks! It's time for a big update. As many of you are probably
>>> aware, I maintain the RPMs of Review Board that live in Fedora's EPEL
>>> project[1] (Extra Packages for Enterprise Linux).
>>>
>>
>> Thanks for your work on this Stephen. No complaints from me, both a clean
>> install and an upgrade worked without issue.
>>
>> One thing I noticed was that the ReviewBoard package doesn't require
>> uglify-js which is required when running 'rb-site manage /path/to/site
>> collectstatic'. It might be worth adding that in a future release, I
>> believe it's only a build dependency at the moment.
>>
>> --
>> 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 reviewboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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 reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

2015-12-16 Thread Stephen Gallagher

On Tue, Dec 15, 2015 at 10:18 AM Ken Erickson  wrote:

> Done
>
> On Tuesday, December 15, 2015 at 4:19:50 AM UTC-7, Stephen Gallagher wrote:
>>
>> Ken, Cian and Sean: since you have had positive experiences, would you
>> mind signing into Bodhi (instructions in the original message for this
>> thread) and providing positive karma? If all three of you did so, this can
>> go to the stable repo immediately. Otherwise, I have to wait until Friday
>> to push it without karma.
>
>

Thanks, folks! The Bodhi update now has sufficient karma and is being
pushed to the stable repositories. It should be available to all users
within 24 hours (as the mirrors sync).

-- 
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 reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

Re: Suddenly getting a Error data : A repository was not found at the specified path.

Re: GitLab hosting stopped working

Suddenly getting a Error data : A repository was not found at the specified path.

Re: GitLab hosting stopped working

Re: GitLab hosting stopped working

Re: GitLab hosting stopped working

Re: GitLab hosting stopped working

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

Re: [Testing Needed] Review Board 2.5.2 for RHEL/CentOS 7

10 matches

Site Navigation

Mail list logo

Footer information