Re: GitLab hosting stopped working

2015-12-17 Thread Ian
Oh sorry I thought you meant total repositories on the server. This user only has access to 1 group and 6 repositories under that. Ian On Wednesday, December 16, 2015 at 11:58:45 PM UTC-8, Christian Hammond wrote: > > Okay, this is likely the issue. The repositories can't be found because we

Re: GitLab hosting stopped working

2015-12-17 Thread Christian Hammond
Hmm, okay. In that case, logged in as the user, can you try accessing: http:///api/v3/groups/ See what that payload looks like, and if the repository you expect is in there anywhere. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, I

Extension - Inject CSS when loading a review for a specific user

2015-12-17 Thread Michael Bell
Hi, Im on the RB 2.5.2. I am writing an extension to inject CSS into a review (/r/[xx]) but only for a particular user. So when the review page loads, if user is xyz, inject the CSS, if not, do nothing. I tried using a TemplateHook to inject the CSS onto specific pages. It worked, however I c

Re: GitLab hosting stopped working

2015-12-17 Thread Ian
Well, I got something. I went to the Hosting Account in Review Board's admin UI and copied the private_token out of the Data box. Then I did this one. curl --header "PRIVATE-TOKEN: " "https:///api/v3/groups/" That said {"message":"401 Unauthorized"} Then I logged into the GitLab web page, we

Re: GitLab hosting stopped working

2015-12-17 Thread Christian Hammond
We store the token in an encrypted form, which is why you're getting that error. You can figure out the value to insert into there by doing: $ rb-site manage /path/to/site shell >>> from reviewboard.scmtools.crypto_utils import encrypt_password >>> print encrypt_password('') That should give you

Re: GitLab hosting stopped working

2015-12-17 Thread Ian
So close. That gave me a different token value from the original one, but now I'm back to "A repository with this name was not found on this group, or your user may not have access to it." Ian On Thursday, December 17, 2015 at 1:37:01 AM UTC-8, Christian Hammond wrote: > > We store the token i

Re: GitLab hosting stopped working

2015-12-17 Thread Christian Hammond
We're decrypting the value before plugging it into any requests. Running that same script but with decrypt_password (and specifying the stored token) will give you what we're passing on to the server in a request. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://w

Re: GitLab hosting stopped working

2015-12-17 Thread Ian
Finally I figured it out. Looking a little closer at the JSON, I noticed that the name and path differ by case, i.e. "name": "MyProject" and "path": "myproject". Review Board apparently wants the name and not the path. (I swear RB 2.0 wanted the path...) Which is kind of weird because now it

Re: GitLab hosting stopped working

2015-12-17 Thread Christian Hammond
Glad it works! RB 2.0 definitely needed the name and not the path, as our hosting services construct the URLs based on that data. As far as casing goes, though, that's entirely up to the GitLab API, and it's possible they've made a change in what it considers valid for lookups, breaking your repos

GitHub-style review flow

2015-12-17 Thread Veit Guna
Hi. In a project we're using subversion as our SCM. Since I like the GitHub review style very much, I would like to do the same with reviewboard. For this the planned process would look like the following: - The "master" branch is trunk - All code changes are done within separate feature branche

Re: GitHub-style review flow

2015-12-17 Thread Christian Hammond
Just for you, Veit: https://reviews.reviewboard.org/r/7812/ I know this isn't a full answer to everything in your e-mail (it's nearly 3AM and I'm about to crash), but this should let you at least use api-get without a local checkout by passing --server=. To answer your last question, the old-styl

Aw: Re: GitHub-style review flow

2015-12-17 Thread Veit Guna
Wow, thanks Christian - that was quick :)!   I'll take a look at the github hook. Thanks!   Gesendet: Donnerstag, 17. Dezember 2015 um 11:47 Uhr Von: "Christian Hammond" An: "reviewboard@googlegroups.com" Betreff: Re: GitHub-style review flow Just for you, Veit: https://reviews.reviewboard

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

2015-12-17 Thread Cian Mc Govern
On 16 December 2015 at 20:02, Christian Hammond wrote: > 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..

Re: GitHub-style review flow

2015-12-17 Thread Veit Guna
Hi Christian. I've applied your patch to my rbt and it seems to work, thanks for that :)! But looking at /review-requests/ shows the requests, but the attributes "branch" and "bugs" are always empty, although these attributes are set on the request. I also changed to values through the UI, but wi

Re: GitHub-style review flow

2015-12-17 Thread Christian Hammond
Hi Veit, That definitely seems wrong. These are published review requests, not drafts? Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On Thu, Dec 17, 2015 at 2:46 PM, Veit Guna wrote: > Hi Christ