Yea. I do not know about the web API, I'll have to look into that.
On Jun 9, 2012 2:02 AM, Dado Feigenblatt d...@dado.org wrote:
Hi Ryan, thanks for the reply.
Unfortunately my server doesn't understand that request.
I'm running ReviewBoard 1.6.3.
I see you don't have '/api/' in your URL.
I am new to RB, so please bear with me if this is a stupid question.
I installed RB 1.6.6 as a PoC a week ago. It ran fine, albeit I never
managed to upload a git diff --full-index --- it always complained about
the first file in the diff, saying that said file with hash hash couldn't
be found
Hi,
Do you get any errors at all when trying to add the repository?
Is the Review Board server behind a proxy at all? The lack of a response
makes me wonder if it can't reach GitHub.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. -
Thanks for the quick reply!
No errors. I literally click the Add Repository button and nothing
happens. This is with zero repositories configured yet, so RB has no
knowledge of github yet. No proxy involved either. I ran ngrep on localhost
to see whether perhaps it was blocked somehow on
Update: after having stepped away for a few hours, I was able to add a
repository now. Weird.
However, now I am stuck at the next problem. I select Github, add account
name and password and everything else, then click Save. The page returns
with a notification saying
The authenticity of the
This command
ssh-keyscan -H github.com data/.ssh/known_hosts chown
www-data:www-data
fixed the ssh issue. Now the next problem:
- A repository was not found at the specified path.
Repository type is Git, plan is Private. What needs to go in the Name
field? The repository I want to
Update: had to choose Private Organization, then got owner and name
fields.
Now back to my original problem, before running into the issue of this
thread: I can't post a review. I created a diff via git diff --full-index
and uploaded it via the web interface, only to get a 500:
Something
Hi,
I was on RB 1.5.5 , then an upgrade of the Ubuntu OS to 12.04 LTS then
broke reviewboard (so it wanted to upgrade) so I ran an upgrade which has
not been successful. (Note I believe Python was upgraded from 2.6 to 2.7)
It seems to work until you go to the /admin/ areas.
Rebuilding
Clearly some problems with the new change. I'm looking into each of them.
We'll probably put out another release soon. Thanks for reporting them, and
sorry, no immediate answers, but I may be able to get you an early build to
test with.
Christian
--
Christian Hammond - chip...@chipx86.com
For what it's worth, the lack of a response was probably some networking
issue between you and GitHub. (It may have been GitHub's server failing to
respond and timing out).
I believe the required password issue is something I already have a fix
for, so I'll get you a build soon to test that.
I'm realizing this doesn't make any sense at all. It's claiming that
repository.extra_data is a string, but it shouldn't be able to be one.
How familiar are you with Python? Would you mind trying something for me?
Run:
$ rb-site manage /path/to/site shell
from
Your upgrade apparently also upgraded to Review Board 1.6.7, which has many
significant changes. And that upgrade failed, because of the django_session
issue.
I've seen that django_session error before. Not sure what the cause is, but
basically, that's a database index that was created, and
On Sunday, June 10, 2012 1:04:30 PM UTC+9:30, Christian Hammond wrote:
Your upgrade apparently also upgraded to Review Board 1.6.7, which has
many significant changes. And that upgrade failed, because of the
django_session issue.
I've seen that django_session error before. Not sure what
No, that should never have been reached. That shows you're in some
half-modified database state, which shouldn't have happened, given that
database transactions are used during the evolution and the earlier error
should have prevented the other modifications.
At this point, I really wish you had
I'ts been a couple of years since I wrote Python but I think I can still do
it ;)
Here's the output. Org and repo names changed to myFoo (they happen to be
the same):
print repo.extra_data
{u'bug_tracker_use_hosting': False, u'github_private_org_name': u'myFoo',
For what it's worth, the lack of a response was probably some networking
issue between you and GitHub. (It may have been GitHub's server failing to
respond and timing out).
I doubt it. Remember, this was a naked install, with zero data. Clicking
the Add Repository button on the Dashboard
It may not be your network, but possibly GitHub's SSH servers were the
problem? I've seen that happen before. There's certainly nothing on the RB
side that should block that long. Anyway, please let me know if that
happens again and we'll poke more at it.
I'll have a build for you soon to test
17 matches
Mail list logo
