Hi,
I recently changed the IP Address of my Linux Box hosting the RB Site.
Post to this, I am unable to login as any user.
I tried to reset the password using :
$ rb-site manage /path/to/site shell
from django.contrib.auth.models import User
u = User.objects.get(username=admin)
I just noticed that ElementRiver has an eclipse based plugin for code
reviews. It could be nice to start reviews right in the IDE but
ReviewBoard has a lot of essential features too. An integration would
be interesting...
Done.
http://code.google.com/p/reviewboard/issues/detail?id=1966
On Jan 28, 8:12 pm, Christian Hammond chip...@chipx86.com wrote:
I agree. Would you mind filing a bug on that?
Christian
On Friday, January 28, 2011, Daniel da.s...@gmail.com wrote:
When I upload multiple screenshots using
Hi,
First of all, thanks for a great review tool. We have been using
ReviewBoard for over a year now and it has become an invaluable tool for us.
We recently got a new server and I took the opportunity to update our
ReviewBoard installation to 1.5.2 (from a really ancient 1.0alpha version)
Authentication will be going through your AD server. Sounds like some
configuration or communication problem there?
You should be able to log in as the original admin user. If so, turn
on logging (assuming it's off) and see if it says there are issues
talking to your AD server.
Christian
On
Hi David.
Well that doesn't sound so good. Can't say I've seen that, but will
see if I can repro it.
What database are you using?
Can you turn on logging and see what the last entries are when this happens?
Christian
On Monday, January 31, 2011, David Dibben dib...@ieee.org wrote:
Hi,
Hi Daniel,
We actually had an Eclipse plugin a while back, but there was nobody
to continue maintaining it so it fell apart (and definitely won't work
in RB 1.6).
ReviewMate seems interesting. I need to look at that more. Can't tell
if it's a competitor or a possible integration point, but it
hi, I am new to setting up reviewboard. I am using SVN, mySql, and I
am able to submit review request manually by creating the diff file
and attaching it to the review request.
I am trying to use post-review with pre-committed code in order to
automate the creation of the diff file.
I been
Hi,
This looks to be a configuration issue.
I assume the root of the SVN repository is /svn, and inter is a directory
within that, am I correct?
Review Board's repository configuration needs to point to the very root of
the SVN repository, rather than a directory within it. What's happening is
Hi Christian,
I think i know what the issue is.
The CVS server does not accept ssh connection without the command
option.
It does not allow to login into the shell.
The way to get the CVS data would be to invoke the SSH connection
along with the cvs command.
From the code, i see that you login
Work will need to be done to implement this in rbssh. I'll work a bit on it
and, if I can get that and another rbssh bug fixed in the next few days,
I'll get a release out.
Sorry for the delay. This is a new piece of code needed to work around some
other large problems, but I know it's blocking
Comment #8 on issue 1961 by anthony@gmail.com: Git SSH repository:
Cannot spawn rbssh
http://code.google.com/p/reviewboard/issues/detail?id=1961
I tried uploading a key but RB is trying to load the key from the home
directory still.
--
You received this message because you are
Comment #9 on issue 1961 by anthony@gmail.com: Git SSH repository:
Cannot spawn rbssh
http://code.google.com/p/reviewboard/issues/detail?id=1961
Ahh.. generate_user_key in sshutils.py just returns the found key in the
home directory even if a key is uploaded.
--
You received this
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 1967 by shaheen@quanteragroup.com: post-review 0.3 unexpected
diff behaviour and git repository fatal error
http://code.google.com/p/reviewboard/issues/detail?id=1967
*NOTE: Do not post confidential information in this
Comment #1 on issue 1967 by shaheen@quanteragroup.com: post-review 0.3
unexpected diff behaviour and git repository fatal error
http://code.google.com/p/reviewboard/issues/detail?id=1967
In the Review Board administration portal, I have a repository with the
following fields filled
Comment #11 on issue 1961 by anthony@gmail.com: Git SSH repository:
Cannot spawn rbssh
http://code.google.com/p/reviewboard/issues/detail?id=1961
After I hit save to save the ssh git repository, the SSH session just seems
to die for some reason and then RB times out. Here's the RB
Comment #5 on issue 1963 by chip...@gmail.com: HTTP 500 when
posting/updating review request via post-review
http://code.google.com/p/reviewboard/issues/detail?id=1963
We should handle it gracefully.
As for debugging the server connection, it appears to be entirely an issue
on your end,
Updates:
Status: NeedInfo
Comment #1 on issue 1965 by chip...@gmail.com: Installed ReviewBoard on
CentOS 5.5, rebooted CentOS, ReviewBoard now fails.
http://code.google.com/p/reviewboard/issues/detail?id=1965
At first glance, it looks like you may have an e-mail address on some user
Comment #2 on issue 1965 by kusem...@gmail.com: Installed ReviewBoard on
CentOS 5.5, rebooted CentOS, ReviewBoard now fails.
http://code.google.com/p/reviewboard/issues/detail?id=1965
Actually, these errors are what shows up when mysql server isn't running -
uhm, what? well, anyway,
Updates:
Status: SetupIssue
Comment #3 on issue 1965 by chip...@gmail.com: Installed ReviewBoard on
CentOS 5.5, rebooted CentOS, ReviewBoard now fails.
http://code.google.com/p/reviewboard/issues/detail?id=1965
Hah, well that is weird. Maybe Django's e-mail code ended up getting
Comment #12 on issue 1961 by chip...@gmail.com: Git SSH repository: Cannot
spawn rbssh
http://code.google.com/p/reviewboard/issues/detail?id=1961
For the key, it specifically looks for id_dsa or id_rsa. It sounds like
maybe it was still either looking in the wrong location, or you manually
Comment #3 on issue 1967 by shaheen@quanteragroup.com: post-review 0.3
unexpected diff behaviour and git repository fatal error
http://code.google.com/p/reviewboard/issues/detail?id=1967
Thank you for your reply. I realize the oversight now with regards to only
providing a path and not
Updates:
Status: SetupIssue
Owner: chipx86
Labels: -Type-Defect Type-Support
Comment #4 on issue 1967 by chip...@gmail.com: post-review 0.3 unexpected
diff behaviour and git repository fatal error
http://code.google.com/p/reviewboard/issues/detail?id=1967
Review Board
23 matches
Mail list logo