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.
