Re: rbt post using Mercurial
I get a repo is not local error. It looks like the code is trying to get
the file contents as of a specific changeset from a remote server via ssh.
I'm not sure if there is a way to do that without cloning the repo. If
there repo is available via a webbrowser, then the file can be retrieved
via the /raw interface. That's because the server will ask the repo located
on the same server for the file.
To me, it looks like what it's trying to do cannot be don via ssh.
-Ali
On Mon, Jun 16, 2014 at 10:47 PM, Christian Hammond
christ...@beanbaginc.com wrote:
What happens if you remove the —cwd line?
We probably want to conditionalize setting that.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 16, 2014 at 9:39:08 AM, Ali Ghorashi (agho...@gmail.com) wrote:
I'm still getting the file not found error when I do a rbt post -u -d.
Here is the error (I'm trying a different file than before.)
Error data: {u'stat': u'fail', u'file': u'src/SIPSA.cpp', u'err':
{u'msg': u'The file was not found in the repository.', u'code': 207},
u'revision': u'79c09fdfad23'}
I've been tracing through the code to see where the problem is. I added
the following debug message to the popen method of SCMTool:
logging.debug('SCMTool.popen command = %s',command)
And this is what I'm getting:
SCMTool.popen command = [u'hg', u'--noninteractive', u'--repository',
u'ssh://source.cei.com//home/hg/projects/sipsa/core/', u'--cwd', u'ssh://
source.cei.com//home/hg/projects/sipsa/core/', u'--config',
u'ui.ssh=rbssh', u'cat', u'--rev', u'79c09fdfad23', u'src/SIPSA.cpp']
If I read this right, it looks like the current working directory is being
set to ssh://. Is that correct? I'm not sure Mercurial can use a
remote ssh path as the current directory. When I paste the command into a
shell, Mercurial (version 2.8.2) says:
abort: No such file or directory: 'ssh://
source.cei.com//home/hg/projects/sipsa/core'
Thanks
-Ali
On Thursday, June 12, 2014 1:51:14 PM UTC-6, Ali Ghorashi wrote:
Changeset 79c09fdfad23 did not include src/Message.h. The last time
src/Message.h was in the changeset was on rev 68:2ed54119d47d (33 commits
ago). With that said, I verified that the latest version of src/Message.h
(prior to this last change) is in the repo.
On Thu, Jun 12, 2014 at 1:42 PM, Christian Hammond
christ...@beanbaginc.com wrote:
The thing I’d want to check first is that src/Message.h, revision
79c09fdfad23 is actually in the repository that Review Board is pointed to.
Can you verify that? If that’s not the case, then either that repository
doesn’t have the latest-and-greatest (which is important), or there’s some
issue with the range being posted from your local copy.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 12, 2014 at 12:36:45 PM, Ali Ghorashi (agho...@gmail.com) wrote:
Thanks for clearing that up.
Is there any file/function I can put some debug statements in to see
what the problem is? I have't had time to start tracing though the code yet.
On Thursday, June 12, 2014 1:32:36 PM UTC-6, Christian Hammond wrote:
The ‘hg svn’ errors are normal in debug output, if the appropriate
extension is not installed or it’s not a hg svn repository.
Review Board fetches the full contents of the files referenced in the
diffs in order to generate a side-by-side diff viewer that can be analyzed
and expanded. Because of this, we need some repository to talk to that has
the most up-to-date commits.
Christian
--
Christian Hammond - chri...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 12, 2014 at 8:17:49 AM, Ali Ghorashi (agh...@gmail.com) wrote:
Are the hg svn errors normal?
I'm also confused about another thing: Why does the reviewboard server
needs to know where the main Mercurial repo is? What if one does not exist?
In a distributed source control system, all the data is available to the
rbt tool. It should be able to post a complete diff without the server
having to know any specifics about the repo.
Any help would be appreciated.
Thanks
-Ali
On Wednesday, June 11, 2014 9:43:45 AM UTC-6, Ali Ghorashi wrote:
Thanks Christian,
See the attached file for the debug output. There is nothing special
about the repo setup: I don't have any branches. Everything up to
changeset
100:79c09fdfad23 is pushed into the main repo. I changed a file with
changeset: 101:1170d2410ead and then did a rbt post. To say it a
different way: when I type hg out, I only get changeset 101:1170d2410ead.
-Ali
On Tuesday, June 10, 2014 5:41:10 PM UTC-6, Christian Hammond wrote:
Hi Ali,
Can you run the ‘rbt post’ with —debug and show me the result?
Also, what does your branch structure look
Re: rbt post using Mercurial
I'm still getting the file not found error when I do a rbt post -u -d. Here
is the error (I'm trying a different file than before.)
Error data: {u'stat': u'fail', u'file': u'src/SIPSA.cpp', u'err':
{u'msg': u'The file was not found in the repository.', u'code': 207},
u'revision': u'79c09fdfad23'}
I've been tracing through the code to see where the problem is. I added the
following debug message to the popen method of SCMTool:
logging.debug('SCMTool.popen command = %s',command)
And this is what I'm getting:
SCMTool.popen command = [u'hg', u'--noninteractive', u'--repository',
u'ssh://source.cei.com//home/hg/projects/sipsa/core/', u'--cwd',
u'ssh://source.cei.com//home/hg/projects/sipsa/core/', u'--config',
u'ui.ssh=rbssh', u'cat', u'--rev', u'79c09fdfad23', u'src/SIPSA.cpp']
If I read this right, it looks like the current working directory is being
set to ssh://. Is that correct? I'm not sure Mercurial can use a
remote ssh path as the current directory. When I paste the command into a
shell, Mercurial (version 2.8.2) says:
abort: No such file or directory:
'ssh://source.cei.com//home/hg/projects/sipsa/core'
Thanks
-Ali
On Thursday, June 12, 2014 1:51:14 PM UTC-6, Ali Ghorashi wrote:
Changeset 79c09fdfad23 did not include src/Message.h. The last time
src/Message.h was in the changeset was on rev 68:2ed54119d47d (33 commits
ago). With that said, I verified that the latest version of src/Message.h
(prior to this last change) is in the repo.
On Thu, Jun 12, 2014 at 1:42 PM, Christian Hammond
christ...@beanbaginc.com wrote:
The thing I’d want to check first is that src/Message.h, revision
79c09fdfad23 is actually in the repository that Review Board is pointed to.
Can you verify that? If that’s not the case, then either that repository
doesn’t have the latest-and-greatest (which is important), or there’s some
issue with the range being posted from your local copy.
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 12, 2014 at 12:36:45 PM, Ali Ghorashi (agho...@gmail.com) wrote:
Thanks for clearing that up.
Is there any file/function I can put some debug statements in to see what
the problem is? I have't had time to start tracing though the code yet.
On Thursday, June 12, 2014 1:32:36 PM UTC-6, Christian Hammond wrote:
The ‘hg svn’ errors are normal in debug output, if the appropriate
extension is not installed or it’s not a hg svn repository.
Review Board fetches the full contents of the files referenced in the
diffs in order to generate a side-by-side diff viewer that can be analyzed
and expanded. Because of this, we need some repository to talk to that has
the most up-to-date commits.
Christian
--
Christian Hammond - chri...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 12, 2014 at 8:17:49 AM, Ali Ghorashi (agh...@gmail.com) wrote:
Are the hg svn errors normal?
I'm also confused about another thing: Why does the reviewboard server
needs to know where the main Mercurial repo is? What if one does not exist?
In a distributed source control system, all the data is available to the
rbt tool. It should be able to post a complete diff without the server
having to know any specifics about the repo.
Any help would be appreciated.
Thanks
-Ali
On Wednesday, June 11, 2014 9:43:45 AM UTC-6, Ali Ghorashi wrote:
Thanks Christian,
See the attached file for the debug output. There is nothing special
about the repo setup: I don't have any branches. Everything up to
changeset
100:79c09fdfad23 is pushed into the main repo. I changed a file with
changeset: 101:1170d2410ead and then did a rbt post. To say it a
different way: when I type hg out, I only get changeset 101:1170d2410ead.
-Ali
On Tuesday, June 10, 2014 5:41:10 PM UTC-6, Christian Hammond wrote:
Hi Ali,
Can you run the ‘rbt post’ with —debug and show me the result?
Also, what does your branch structure look like? It’ll be helpful
for me to know what the commit ID is for the change you’re trying to
post,
as well as the nearest upstream branch.
Christian
--
Christian Hammond - chri...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 10, 2014 at 9:33:59 AM, Ali Ghorashi (agh...@gmail.com) wrote:
Ok. I must be missing something. Here is what I'm trying on a fresh
reviewboard install
1) Configure a repo with a full path: ssh://source.xxx.com//path_to_
project
2) Enter user name and password
3) Push all changes to the Mercurial Repo
4) Change a file
5) Commit the file (no push)
6) Run rbt post
7) Get an error saying Got API Error 207 (HTTP code 400): The file
was not found in the repository
What am I doing wrong?
-Ali
On Monday, June 9, 2014 2:36:09 PM
Re: rbt post using Mercurial
Are the hg svn errors normal?
I'm also confused about another thing: Why does the reviewboard server
needs to know where the main Mercurial repo is? What if one does not exist?
In a distributed source control system, all the data is available to the
rbt tool. It should be able to post a complete diff without the server
having to know any specifics about the repo.
Any help would be appreciated.
Thanks
-Ali
On Wednesday, June 11, 2014 9:43:45 AM UTC-6, Ali Ghorashi wrote:
Thanks Christian,
See the attached file for the debug output. There is nothing special about
the repo setup: I don't have any branches. Everything up to changeset
100:79c09fdfad23 is pushed into the main repo. I changed a file with
changeset: 101:1170d2410ead and then did a rbt post. To say it a
different way: when I type hg out, I only get changeset 101:1170d2410ead.
-Ali
On Tuesday, June 10, 2014 5:41:10 PM UTC-6, Christian Hammond wrote:
Hi Ali,
Can you run the ‘rbt post’ with —debug and show me the result?
Also, what does your branch structure look like? It’ll be helpful for me
to know what the commit ID is for the change you’re trying to post, as well
as the nearest upstream branch.
Christian
--
Christian Hammond - chri...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 10, 2014 at 9:33:59 AM, Ali Ghorashi (agh...@gmail.com) wrote:
Ok. I must be missing something. Here is what I'm trying on a fresh
reviewboard install
1) Configure a repo with a full path: ssh://
source.xxx.com//path_to_project
2) Enter user name and password
3) Push all changes to the Mercurial Repo
4) Change a file
5) Commit the file (no push)
6) Run rbt post
7) Get an error saying Got API Error 207 (HTTP code 400): The file was
not found in the repository
What am I doing wrong?
-Ali
On Monday, June 9, 2014 2:36:09 PM UTC-6, Ali Ghorashi wrote:
Update: The rbt post 101 command does not work either.
I should mention that I'm using mercurial via ssh. In other words, my
server URL is ssh://xxx.xxx.com
On Monday, June 9, 2014 12:45:48 PM UTC-6, Ali Ghorashi wrote:
Thanks for the reply Christian.
I posted the wrong error message. The error is:
ERROR: Error uploading diff
The file was not found in the repository. (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
Successive attempts with the -u options (i.e. rbt post -u) generate the
same error and no diff is attached.
I tried to run the post command with the debug option and got the
following error:
Making HTTP POST request to
http://reviews.cei.com/reviews/api/review-requests/23/diffs/
Got API Error 207 (HTTP code 400): The file was not found in the
repository.
Error data: {u'stat': u'fail', u'file': u'.cproject', u'err':
{u'msg': u'The file was not found in the repository.', u'code': 207},
u'revision': u'1b3944112e43'}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.6', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/__init__.py,
line 422, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 769, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 545, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
If I do a rbt post 101 instead of the first rb post the operation
is successful.
-Ali
On Wednesday, June 4, 2014 2:49:41 PM UTC-6, Christian Hammond wrote:
They don’t need to specify a version number. It is using the tip.
What’s happening with that error is that you’ve already posted a
review request representing the commit that you’ve posted for review.
Review Board tries to keep a 1-to-1 mapping of commit ID and review
request, and so it’s noticing that that particular commit is already in
the
database.
If you want to update it, you’d pass -u to rbt post.
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 4, 2014 at 11:29:25 AM, Ali Ghorashi (agh...@gmail.com) wrote:
Hello All,
I'm evaluating Review Board. I'm running RB version 2.0.1 on Centos
6.5 with Mercurial v 2.8.3.
My question is regarding the rbt post command: After I do a commit
and run rbt post, I get the following error:
ERROR: Error creating review request: Review request with this commit
ID already exists in the repository. (HTTP 409, API Error
Re: rbt post using Mercurial
Thanks for clearing that up.
Is there any file/function I can put some debug statements in to see what
the problem is? I have't had time to start tracing though the code yet.
On Thursday, June 12, 2014 1:32:36 PM UTC-6, Christian Hammond wrote:
The ‘hg svn’ errors are normal in debug output, if the appropriate
extension is not installed or it’s not a hg svn repository.
Review Board fetches the full contents of the files referenced in the
diffs in order to generate a side-by-side diff viewer that can be analyzed
and expanded. Because of this, we need some repository to talk to that has
the most up-to-date commits.
Christian
--
Christian Hammond - chri...@beanbaginc.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 12, 2014 at 8:17:49 AM, Ali Ghorashi (agh...@gmail.com
javascript:) wrote:
Are the hg svn errors normal?
I'm also confused about another thing: Why does the reviewboard server
needs to know where the main Mercurial repo is? What if one does not exist?
In a distributed source control system, all the data is available to the
rbt tool. It should be able to post a complete diff without the server
having to know any specifics about the repo.
Any help would be appreciated.
Thanks
-Ali
On Wednesday, June 11, 2014 9:43:45 AM UTC-6, Ali Ghorashi wrote:
Thanks Christian,
See the attached file for the debug output. There is nothing special
about the repo setup: I don't have any branches. Everything up to changeset
100:79c09fdfad23 is pushed into the main repo. I changed a file with
changeset: 101:1170d2410ead and then did a rbt post. To say it a
different way: when I type hg out, I only get changeset 101:1170d2410ead.
-Ali
On Tuesday, June 10, 2014 5:41:10 PM UTC-6, Christian Hammond wrote:
Hi Ali,
Can you run the ‘rbt post’ with —debug and show me the result?
Also, what does your branch structure look like? It’ll be helpful for
me to know what the commit ID is for the change you’re trying to post, as
well as the nearest upstream branch.
Christian
--
Christian Hammond - chri...@beanbaginc.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 10, 2014 at 9:33:59 AM, Ali Ghorashi (agh...@gmail.com) wrote:
Ok. I must be missing something. Here is what I'm trying on a fresh
reviewboard install
1) Configure a repo with a full path: ssh://
source.xxx.com//path_to_project
2) Enter user name and password
3) Push all changes to the Mercurial Repo
4) Change a file
5) Commit the file (no push)
6) Run rbt post
7) Get an error saying Got API Error 207 (HTTP code 400): The file was
not found in the repository
What am I doing wrong?
-Ali
On Monday, June 9, 2014 2:36:09 PM UTC-6, Ali Ghorashi wrote:
Update: The rbt post 101 command does not work either.
I should mention that I'm using mercurial via ssh. In other words, my
server URL is ssh://xxx.xxx.com
On Monday, June 9, 2014 12:45:48 PM UTC-6, Ali Ghorashi wrote:
Thanks for the reply Christian.
I posted the wrong error message. The error is:
ERROR: Error uploading diff
The file was not found in the repository. (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
Successive attempts with the -u options (i.e. rbt post -u) generate
the same error and no diff is attached.
I tried to run the post command with the debug option and got the
following error:
Making HTTP POST request to
http://reviews.cei.com/reviews/api/review-requests/23/diffs/
Got API Error 207 (HTTP code 400): The file was not found in the
repository.
Error data: {u'stat': u'fail', u'file': u'.cproject', u'err':
{u'msg': u'The file was not found in the repository.', u'code': 207},
u'revision': u'1b3944112e43'}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.6', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/__init__.py,
line 422, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 769, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 545, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
If I do a rbt post 101 instead of the first rb post the operation
is successful.
-Ali
On Wednesday, June 4, 2014 2:49:41 PM UTC-6, Christian Hammond wrote:
They don’t need to specify a version number. It is using the tip.
What’s happening
Re: rbt post using Mercurial
Thanks Christian,
See the attached file for the debug output. There is nothing special about
the repo setup: I don't have any branches. Everything up to changeset
100:79c09fdfad23 is pushed into the main repo. I changed a file with
changeset: 101:1170d2410ead and then did a rbt post. To say it a
different way: when I type hg out, I only get changeset 101:1170d2410ead.
-Ali
On Tuesday, June 10, 2014 5:41:10 PM UTC-6, Christian Hammond wrote:
Hi Ali,
Can you run the ‘rbt post’ with —debug and show me the result?
Also, what does your branch structure look like? It’ll be helpful for me
to know what the commit ID is for the change you’re trying to post, as well
as the nearest upstream branch.
Christian
--
Christian Hammond - chri...@beanbaginc.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 10, 2014 at 9:33:59 AM, Ali Ghorashi (agh...@gmail.com
javascript:) wrote:
Ok. I must be missing something. Here is what I'm trying on a fresh
reviewboard install
1) Configure a repo with a full path: ssh://
source.xxx.com//path_to_project
2) Enter user name and password
3) Push all changes to the Mercurial Repo
4) Change a file
5) Commit the file (no push)
6) Run rbt post
7) Get an error saying Got API Error 207 (HTTP code 400): The file was
not found in the repository
What am I doing wrong?
-Ali
On Monday, June 9, 2014 2:36:09 PM UTC-6, Ali Ghorashi wrote:
Update: The rbt post 101 command does not work either.
I should mention that I'm using mercurial via ssh. In other words, my
server URL is ssh://xxx.xxx.com
On Monday, June 9, 2014 12:45:48 PM UTC-6, Ali Ghorashi wrote:
Thanks for the reply Christian.
I posted the wrong error message. The error is:
ERROR: Error uploading diff
The file was not found in the repository. (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
Successive attempts with the -u options (i.e. rbt post -u) generate the
same error and no diff is attached.
I tried to run the post command with the debug option and got the
following error:
Making HTTP POST request to
http://reviews.cei.com/reviews/api/review-requests/23/diffs/
Got API Error 207 (HTTP code 400): The file was not found in the
repository.
Error data: {u'stat': u'fail', u'file': u'.cproject', u'err':
{u'msg': u'The file was not found in the repository.', u'code': 207},
u'revision': u'1b3944112e43'}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.6', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/__init__.py,
line 422, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 769, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 545, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
If I do a rbt post 101 instead of the first rb post the operation is
successful.
-Ali
On Wednesday, June 4, 2014 2:49:41 PM UTC-6, Christian Hammond wrote:
They don’t need to specify a version number. It is using the tip.
What’s happening with that error is that you’ve already posted a
review request representing the commit that you’ve posted for review.
Review Board tries to keep a 1-to-1 mapping of commit ID and review
request, and so it’s noticing that that particular commit is already in
the
database.
If you want to update it, you’d pass -u to rbt post.
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 4, 2014 at 11:29:25 AM, Ali Ghorashi (agh...@gmail.com) wrote:
Hello All,
I'm evaluating Review Board. I'm running RB version 2.0.1 on Centos 6.5
with Mercurial v 2.8.3.
My question is regarding the rbt post command: After I do a commit
and run rbt post, I get the following error:
ERROR: Error creating review request: Review request with this commit
ID already exists in the repository. (HTTP 409, API Error 227)
But if I look up the version id (id=100 let's say) and do rbt post
100. The command seems to work. After reading the documentation, it seems
like the rbt post should always use the tip when no version is specified.
Is this the expected behavior? Does the user need to specify the
version number every time a new post is created?
Thanks
-Ali
--
Get the Review Board Power Pack at
http://www.reviewboard.org/powerpack/
---
Sign up
rbt setup-repo with Mercurial
Hello All, I have a Mercurial repo and I'm trying to setup the .reviewboardrc file using rbt setup-repo per the documentation. However, it keeps giving me the following error even though I have a Mercurial Repo configured via the admin page. Is this a bug or user error? -Ali -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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: rbt post using Mercurial
Ok. I must be missing something. Here is what I'm trying on a fresh
reviewboard install
1) Configure a repo with a full path: ssh://source.xxx.com//path_to_project
2) Enter user name and password
3) Push all changes to the Mercurial Repo
4) Change a file
5) Commit the file (no push)
6) Run rbt post
7) Get an error saying Got API Error 207 (HTTP code 400): The file was not
found in the repository
What am I doing wrong?
-Ali
On Monday, June 9, 2014 2:36:09 PM UTC-6, Ali Ghorashi wrote:
Update: The rbt post 101 command does not work either.
I should mention that I'm using mercurial via ssh. In other words, my
server URL is ssh://xxx.xxx.com
On Monday, June 9, 2014 12:45:48 PM UTC-6, Ali Ghorashi wrote:
Thanks for the reply Christian.
I posted the wrong error message. The error is:
ERROR: Error uploading diff
The file was not found in the repository. (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
Successive attempts with the -u options (i.e. rbt post -u) generate the
same error and no diff is attached.
I tried to run the post command with the debug option and got the
following error:
Making HTTP POST request to
http://reviews.cei.com/reviews/api/review-requests/23/diffs/
Got API Error 207 (HTTP code 400): The file was not found in the
repository.
Error data: {u'stat': u'fail', u'file': u'.cproject', u'err':
{u'msg': u'The file was not found in the repository.', u'code': 207},
u'revision': u'1b3944112e43'}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.6', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/__init__.py,
line 422, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 769, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 545, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
If I do a rbt post 101 instead of the first rb post the operation is
successful.
-Ali
On Wednesday, June 4, 2014 2:49:41 PM UTC-6, Christian Hammond wrote:
They don’t need to specify a version number. It is using the tip.
What’s happening with that error is that you’ve already posted a review
request representing the commit that you’ve posted for review. Review Board
tries to keep a 1-to-1 mapping of commit ID and review request, and so it’s
noticing that that particular commit is already in the database.
If you want to update it, you’d pass -u to rbt post.
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 4, 2014 at 11:29:25 AM, Ali Ghorashi (agh...@gmail.com) wrote:
Hello All,
I'm evaluating Review Board. I'm running RB version 2.0.1 on Centos 6.5
with Mercurial v 2.8.3.
My question is regarding the rbt post command: After I do a commit and
run rbt post, I get the following error:
ERROR: Error creating review request: Review request with this commit
ID already exists in the repository. (HTTP 409, API Error 227)
But if I look up the version id (id=100 let's say) and do rbt post
100. The command seems to work. After reading the documentation, it seems
like the rbt post should always use the tip when no version is specified.
Is this the expected behavior? Does the user need to specify the version
number every time a new post is created?
Thanks
-Ali
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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.
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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: rbt setup-repo with Mercurial
oops I forgot to attach it. The error is: No Mercurial repository found or selected for http://reviews.cei.com/reviews. .reviewboardrc not created. -Ali On Tuesday, June 10, 2014 1:45:08 PM UTC-6, David Trowbridge wrote: I don't see an error in your email. -David On Tue, Jun 10, 2014 at 8:36 AM, Ali Ghorashi agh...@gmail.com javascript: wrote: Hello All, I have a Mercurial repo and I'm trying to setup the .reviewboardrc file using rbt setup-repo per the documentation. However, it keeps giving me the following error even though I have a Mercurial Repo configured via the admin page. Is this a bug or user error? -Ali -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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 javascript:. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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: rbt setup-repo with Mercurial
See attached. On Tuesday, June 10, 2014 1:50:31 PM UTC-6, David Trowbridge wrote: Can you run with --debug and attach the output? -David On Tue, Jun 10, 2014 at 12:48 PM, Ali Ghorashi agh...@gmail.com javascript: wrote: oops I forgot to attach it. The error is: No Mercurial repository found or selected for http://reviews.cei.com/reviews. .reviewboardrc not created. -Ali On Tuesday, June 10, 2014 1:45:08 PM UTC-6, David Trowbridge wrote: I don't see an error in your email. -David On Tue, Jun 10, 2014 at 8:36 AM, Ali Ghorashi agh...@gmail.com wrote: Hello All, I have a Mercurial repo and I'm trying to setup the .reviewboardrc file using rbt setup-repo per the documentation. However, it keeps giving me the following error even though I have a Mercurial Repo configured via the admin page. Is this a bug or user error? -Ali -- Get the Review Board Power Pack at http://www.reviewboard.org/ powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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 javascript:. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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. [ali@dariush core]$ rbt setup-repo -d RBTools 0.6 Python 2.6.6 (r266:84292, Jan 22 2014, 09:42:36) [GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] Running on Linux-2.6.32-431.11.2.el6.x86_64-x86_64-with-centos-6.5-Final Home = /home/ali Current directory = /tmp/sipsa/core Checking for a Subversion repository... Running: svn info --non-interactive Command exited with rc 1: ['svn', 'info', '--non-interactive'] svn: E155007: '/tmp/sipsa/core' is not a working copy --- Checking for a Git repository... Running: git rev-parse --git-dir Command exited with rc 128: ['git', 'rev-parse', '--git-dir'] fatal: Not a git repository (or any of the parent directories): .git --- Checking for a Mercurial repository... Running: hg root Running: hg showconfig Running: hg svn info Command exited with rc 255: ['hg', 'svn', 'info'] hg: unknown command 'svn' Mercurial Distributed SCM basic commands: add add the specified files on the next commit annotate, blame show changeset information by line for each file clone make a copy of an existing repository commit, cicommit the specified files or all outstanding changes diff diff repository (or selected files) exportdump the header and diffs for one or more changesets forgetforget the specified files on the next commit init create a new repository in the given directory log, history show revision history of entire repository or files merge merge working directory with another revision pull pull changes from the specified source push push changes to the specified destination remove, rmremove the specified files on the next commit serve start stand-alone webserver status, stshow changed files in the working directory summary, sum summarize working directory state update, up, checkout, co update working directory (or switch revisions) view start interactive history viewer global options: -R --repository REPO repository root directory or name of overlay bundle file --cwd DIR change working directory -y --noninteractivedo not prompt, automatically pick the first choice for all prompts -q --quiet suppress output -v --verbose enable additional output --config CONFIG [+] set/override config option (use 'section.name=value') --debug enable debugging output --debugger start debugger --encoding ENCODE set the charset encoding (default
Re: rbt setup-repo with Mercurial
Here it is.
On Tuesday, June 10, 2014 1:58:55 PM UTC-6, Ali Ghorashi wrote:
See attached.
On Tuesday, June 10, 2014 1:50:31 PM UTC-6, David Trowbridge wrote:
Can you run with --debug and attach the output?
-David
On Tue, Jun 10, 2014 at 12:48 PM, Ali Ghorashi agh...@gmail.com wrote:
oops I forgot to attach it. The error is:
No Mercurial repository found or selected for
http://reviews.cei.com/reviews. .reviewboardrc not created.
-Ali
On Tuesday, June 10, 2014 1:45:08 PM UTC-6, David Trowbridge wrote:
I don't see an error in your email.
-David
On Tue, Jun 10, 2014 at 8:36 AM, Ali Ghorashi agh...@gmail.com wrote:
Hello All,
I have a Mercurial repo and I'm trying to setup the .reviewboardrc
file using rbt setup-repo per the documentation. However, it keeps
giving
me the following error even though I have a Mercurial Repo configured via
the admin page.
Is this a bug or user error?
-Ali
--
Get the Review Board Power Pack at http://www.reviewboard.org/
powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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.
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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.
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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.
{
links: {
create: {
href: http://reviews.cei.com/reviews/api/repositories/;,
method: POST
},
self: {
href: http://reviews.cei.com/reviews/api/repositories/;,
method: GET
}
},
repositories: [
{
id: 1,
links: {
branches: {
href:
http://reviews.cei.com/reviews/api/repositories/1/branches/;,
method: GET
},
commits: {
href:
http://reviews.cei.com/reviews/api/repositories/1/commits/;,
method: GET
},
delete: {
href:
http://reviews.cei.com/reviews/api/repositories/1/;,
method: DELETE
},
diff_file_attachments: {
href:
http://reviews.cei.com/reviews/api/repositories/1/diff-file-attachments/;,
method: GET
},
info: {
href:
http://reviews.cei.com/reviews/api/repositories/1/info/;,
method: GET
},
self: {
href:
http://reviews.cei.com/reviews/api/repositories/1/;,
method: GET
},
update: {
href:
http://reviews.cei.com/reviews/api/repositories/1/;,
method: PUT
}
},
mirror_path: ,
name: sispa_core,
path:
ssh://aghora...@source.cei.com//home/hg/projects/sipsa/core,
tool: Mercurial,
visible: true
}
],
stat: ok,
total_results: 1
}
Re: rbt setup-repo with Mercurial
Just updated to 0.6.1. It works fine. Now if I could only get my posts to work(https://groups.google.com/forum/#!topic/reviewboard/ZDTY5dyre0U), I'd go home a happy man. On Tue, Jun 10, 2014 at 3:53 PM, Christian Hammond christ...@beanbaginc.com wrote: Hi Ali, That’s very strange. From everything I can tell, this should be working fine. Can you upgrade to RBTools 0.6.1 and try again? It has new logic that could maybe help (even though it should be working already). Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On June 10, 2014 at 1:26:07 PM, Ali Ghorashi (agho...@gmail.com) wrote: Here it is. On Tuesday, June 10, 2014 1:58:55 PM UTC-6, Ali Ghorashi wrote: See attached. On Tuesday, June 10, 2014 1:50:31 PM UTC-6, David Trowbridge wrote: Can you run with --debug and attach the output? -David On Tue, Jun 10, 2014 at 12:48 PM, Ali Ghorashi agh...@gmail.com wrote: oops I forgot to attach it. The error is: No Mercurial repository found or selected for http://reviews.cei.com/reviews. .reviewboardrc not created. -Ali On Tuesday, June 10, 2014 1:45:08 PM UTC-6, David Trowbridge wrote: I don't see an error in your email. -David On Tue, Jun 10, 2014 at 8:36 AM, Ali Ghorashi agh...@gmail.com wrote: Hello All, I have a Mercurial repo and I'm trying to setup the .reviewboardrc file using rbt setup-repo per the documentation. However, it keeps giving me the following error even though I have a Mercurial Repo configured via the admin page. Is this a bug or user error? -Ali -- Get the Review Board Power Pack at http://www.reviewboard.org/pow erpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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. -- Get the Review Board Power Pack at http://www.reviewboard.org/ powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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. -- -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to a topic in the Google Groups reviewboard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/reviewboard/ag8aY4Flh5Q/unsubscribe. To unsubscribe from this group and all its topics, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- -Ali -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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: rbt post using Mercurial
Thanks for the reply Christian.
I posted the wrong error message. The error is:
ERROR: Error uploading diff
The file was not found in the repository. (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
Successive attempts with the -u options (i.e. rbt post -u) generate the
same error and no diff is attached.
I tried to run the post command with the debug option and got the following
error:
Making HTTP POST request to
http://reviews.cei.com/reviews/api/review-requests/23/diffs/
Got API Error 207 (HTTP code 400): The file was not found in the
repository.
Error data: {u'stat': u'fail', u'file': u'.cproject', u'err': {u'msg':
u'The file was not found in the repository.', u'code': 207}, u'revision':
u'1b3944112e43'}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.6', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/__init__.py,
line 422, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 769, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 545, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
If I do a rbt post 101 instead of the first rb post the operation is
successful.
-Ali
On Wednesday, June 4, 2014 2:49:41 PM UTC-6, Christian Hammond wrote:
They don’t need to specify a version number. It is using the tip.
What’s happening with that error is that you’ve already posted a review
request representing the commit that you’ve posted for review. Review Board
tries to keep a 1-to-1 mapping of commit ID and review request, and so it’s
noticing that that particular commit is already in the database.
If you want to update it, you’d pass -u to rbt post.
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 4, 2014 at 11:29:25 AM, Ali Ghorashi (agh...@gmail.com
javascript:) wrote:
Hello All,
I'm evaluating Review Board. I'm running RB version 2.0.1 on Centos 6.5
with Mercurial v 2.8.3.
My question is regarding the rbt post command: After I do a commit and
run rbt post, I get the following error:
ERROR: Error creating review request: Review request with this commit ID
already exists in the repository. (HTTP 409, API Error 227)
But if I look up the version id (id=100 let's say) and do rbt post 100.
The command seems to work. After reading the documentation, it seems like
the rbt post should always use the tip when no version is specified.
Is this the expected behavior? Does the user need to specify the version
number every time a new post is created?
Thanks
-Ali
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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 javascript:.
For more options, visit https://groups.google.com/d/optout.
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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: rbt post using Mercurial
Update: The rbt post 101 command does not work either.
I should mention that I'm using mercurial via ssh. In other words, my
server URL is ssh://xxx.xxx.com
On Monday, June 9, 2014 12:45:48 PM UTC-6, Ali Ghorashi wrote:
Thanks for the reply Christian.
I posted the wrong error message. The error is:
ERROR: Error uploading diff
The file was not found in the repository. (HTTP 400, API Error 207)
Your review request still exists, but the diff is not attached.
Successive attempts with the -u options (i.e. rbt post -u) generate the
same error and no diff is attached.
I tried to run the post command with the debug option and got the
following error:
Making HTTP POST request to
http://reviews.cei.com/reviews/api/review-requests/23/diffs/
Got API Error 207 (HTTP code 400): The file was not found in the
repository.
Error data: {u'stat': u'fail', u'file': u'.cproject', u'err': {u'msg':
u'The file was not found in the repository.', u'code': 207}, u'revision':
u'1b3944112e43'}
Traceback (most recent call last):
File /usr/bin/rbt, line 9, in module
load_entry_point('RBTools==0.6', 'console_scripts', 'rbt')()
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/main.py,
line 134, in main
command.run_from_argv([RB_MAIN, command_name] + args)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/__init__.py,
line 422, in run_from_argv
exit_code = self.main(*args) or 0
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 769, in main
submit_as=self.options.submit_as)
File
/usr/lib/python2.6/site-packages/RBTools-0.6-py2.6.egg/rbtools/commands/post.py,
line 545, in post_request
raise CommandError('\n'.join(error_msg))
rbtools.commands.CommandError: Error uploading diff
If I do a rbt post 101 instead of the first rb post the operation is
successful.
-Ali
On Wednesday, June 4, 2014 2:49:41 PM UTC-6, Christian Hammond wrote:
They don’t need to specify a version number. It is using the tip.
What’s happening with that error is that you’ve already posted a review
request representing the commit that you’ve posted for review. Review Board
tries to keep a 1-to-1 mapping of commit ID and review request, and so it’s
noticing that that particular commit is already in the database.
If you want to update it, you’d pass -u to rbt post.
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com
On June 4, 2014 at 11:29:25 AM, Ali Ghorashi (agh...@gmail.com) wrote:
Hello All,
I'm evaluating Review Board. I'm running RB version 2.0.1 on Centos 6.5
with Mercurial v 2.8.3.
My question is regarding the rbt post command: After I do a commit and
run rbt post, I get the following error:
ERROR: Error creating review request: Review request with this commit ID
already exists in the repository. (HTTP 409, API Error 227)
But if I look up the version id (id=100 let's say) and do rbt post 100.
The command seems to work. After reading the documentation, it seems like
the rbt post should always use the tip when no version is specified.
Is this the expected behavior? Does the user need to specify the version
number every time a new post is created?
Thanks
-Ali
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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.
--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://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.
rbt post using Mercurial
Hello All, I'm evaluating Review Board. I'm running RB version 2.0.1 on Centos 6.5 with Mercurial v 2.8.3. My question is regarding the rbt post command: After I do a commit and run rbt post, I get the following error: ERROR: Error creating review request: Review request with this commit ID already exists in the repository. (HTTP 409, API Error 227) But if I look up the version id (id=100 let's say) and do rbt post 100. The command seems to work. After reading the documentation, it seems like the rbt post should always use the tip when no version is specified. Is this the expected behavior? Does the user need to specify the version number every time a new post is created? Thanks -Ali -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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: Review Board Installation: Bad Request (400)
I had the same problem. When you configure your reviewboard, you have to give it a site name . Some thing like reviewboard.mycompany.com. It doesn't have to be a registered name just make up something. Then when you try to access the reviewboard main page, use the site name (reviewboard.mycompany.com) as the URL. You'll of course need to add the made-up hostname to to your /etc/hosts so your machine can resolve the address. Also, if you setup an extra path to follow your server id, like 'reviews', don't forget to add that to the URL too (e.g. http://reviewboard.mycompany.com/reviews ). I hope this helps. On Wednesday, June 4, 2014 7:04:52 AM UTC-6, Kuldeep singh wrote: Hi All, I have installed reviewboard on a remote machine(Ubuntu with root user). During installation I followed all the steps mentioned on reviewboard site. I used most of configuration default, i mean localhost. But after installation and disabling 000-default site, when I am trying to access reviewboard url, Its always displaying Bad Request (400) message. Now I am very confused why its happening. I am searching solution for last 3 days, but still could not find anything. If any body have any Idea about it, Please help. Thanks Kuldeep Singh -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://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.
