Huh, it happened immediately after modifying the commit (and thus getting a new SHA-1)?
Can you run 'git commit --amend', save, and try posting again? -David On Thu, Jul 10, 2014 at 4:17 PM, Neeraj K <[email protected]> wrote: > I still keep getting the same error. I deleted all drafts and modified the > recent most change in git and ran the command. > > It created another zombie review request(draft) with nothing in it. > > techopss-mbp-10:minted neeraj$ rbt post --parent=release-printerapi --debug > > >>> RBTools 0.6.2 > > >>> Python 2.7.5 (default, Aug 25 2013, 00:04:04) > > [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] > > >>> Running on Darwin-13.1.0-x86_64-i386-64bit > > >>> Home = /Users/neeraj > > >>> Current directory = /Users/neeraj/Work/Minted/minted > > >>> Checking for a Subversion repository... > > >>> Running: svn info --non-interactive > > >>> Command exited with rc 1: ['svn', 'info', '--non-interactive'] > > svn: E155007: '/Users/neeraj/Work/Minted/minted' is not a working copy > > --- > > >>> Checking for a Git repository... > > >>> Running: git rev-parse --git-dir > > >>> Running: git config core.bare > > >>> Running: git rev-parse --show-toplevel > > >>> Running: git symbolic-ref -q HEAD > > >>> Running: git svn info > > >>> repository info: Path: https://svn.minted.com/svn, Base path: > /minted/branches/release-printerapi, Supports changesets: False > > >>> Making HTTP GET request to https://reviewboard.minted.com/api/ > > >>> Running: git rev-parse refs/heads/relprinterapi > > >>> Running: git merge-base 65bb45e65a8049fdcf66d798ed6805d912f507a5 trunk > > >>> Running: git rev-parse e349309cd456b0b2a2265d2028d2468bb2325266 > > >>> Running: git rev-parse release-printerapi > > >>> Running: git status --porcelain --untracked-files=no > > >>> Running: git diff --no-color --no-prefix -r -u > a80831ff6705c3618857a01268962bbd0346251f..65bb45e65a8049fdcf66d798ed6805d912f507a5 > > >>> Running: git svn find-rev e349309cd456b0b2a2265d2028d2468bb2325266 > > >>> Running: git diff --no-color --no-prefix -r -u > e349309cd456b0b2a2265d2028d2468bb2325266..a80831ff6705c3618857a01268962bbd0346251f > > >>> Running: git svn find-rev e349309cd456b0b2a2265d2028d2468bb2325266 > > >>> Running: git log --reverse --pretty=format:%s%n%n%b > ^a80831ff6705c3618857a01268962bbd0346251f > 65bb45e65a8049fdcf66d798ed6805d912f507a5 > > >>> Making HTTP GET request to > https://reviewboard.minted.com/api/review-requests/ > > >>> Making HTTP POST request to > https://reviewboard.minted.com/api/review-requests/ > > >>> Got API Error 227 (HTTP code 409): Review request with this commit ID > already exists in the repository. > > >>> Error data: {u'stat': u'fail', u'err': {u'msg': u'Review request with > this commit ID already exists in the repository.', u'code': 227}} > > Traceback (most recent call last): > > File "/usr/local/bin/rbt", line 8, in <module> > > load_entry_point('RBTools==0.6.2', 'console_scripts', 'rbt')() > > File > "/Library/Python/2.7/site-packages/RBTools-0.6.2-py2.7.egg/rbtools/commands/main.py", > line 134, in main > > command.run_from_argv([RB_MAIN, command_name] + args) > > File > "/Library/Python/2.7/site-packages/RBTools-0.6.2-py2.7.egg/rbtools/commands/__init__.py", > line 416, in run_from_argv > > exit_code = self.main(*args) or 0 > > File > "/Library/Python/2.7/site-packages/RBTools-0.6.2-py2.7.egg/rbtools/commands/post.py", > line 784, in main > > submit_as=self.options.submit_as) > > File > "/Library/Python/2.7/site-packages/RBTools-0.6.2-py2.7.egg/rbtools/commands/post.py", > line 507, in post_request > > raise CommandError("Error creating review request: %s" % e) > > rbtools.commands.CommandError: Error creating review request: Review > request with this commit ID already exists in the repository. (HTTP 409, > API Error 227) > > techopss-mbp-10:minted neeraj$ > > On Thursday, July 10, 2014 3:03:39 PM UTC-7, Neeraj K wrote: >> >> How do I delete a review ? I only see a discarded or submitted option >> under the 'close' menu. I tried discarding but that does not help. >> >> On Thursday, July 10, 2014 12:38:36 PM UTC-7, David Trowbridge wrote: >>> >>> That looks like a different error to me. It looks like you've got some >>> draft review requests (probably from previous versions). I'd suggest >>> deleting them and trying again, or adding '-u' to your rbt post command >>> line to update them. >>> >>> -David >>> >>> >>> On Thu, Jul 10, 2014 at 12:19 PM, Neeraj K <[email protected]> wrote: >>> >>>> Ok I just upgraded to 0.6.2 and I still get the same error >>>> >>>> techopss-mbp-10:minted neeraj$ rbt post >>>> >>>> ERROR: Error creating review request: Review request with this commit >>>> ID already exists in the repository. (HTTP 409, API Error 227) >>>> >>>> techopss-mbp-10:minted neeraj$ rbt post --parent=release-printerapi >>>> --target-groups=all >>>> >>>> ERROR: Error creating review request: Review request with this commit >>>> ID already exists in the repository. (HTTP 409, API Error 227) >>>> >>>> techopss-mbp-10:minted neeraj$ >>>> >>>> On Thursday, July 10, 2014 12:13:49 PM UTC-7, Neeraj K wrote: >>>>> >>>>> Well I am discussing that with the admin. Not sure how much time that >>>>> would take. >>>>> >>>>> On Thursday, July 10, 2014 11:56:18 AM UTC-7, David Trowbridge wrote: >>>>>> >>>>>> What do you mean "in the meantime"?. Is there a reason you can't >>>>>> upgrade to 0.6.2? >>>>>> >>>>>> -David >>>>>> >>>>>> >>>>>> On Thu, Jul 10, 2014 at 11:49 AM, Neeraj K <[email protected]> wrote: >>>>>> >>>>>>> In the meantime isn't there a workaround ? This is causing a lot of >>>>>>> problems for me. >>>>>>> >>>>>>> On Monday, July 7, 2014 11:07:27 AM UTC-7, David Trowbridge wrote: >>>>>>> >>>>>>>> This fix is included in the new 0.6.2 release. >>>>>>>> >>>>>>>> -David >>>>>>>> >>>>>>>> On Jul 7, 2014, at 9:19 AM, Austin Hanson <[email protected]> wrote: >>>>>>>> >>>>>>>> Any chance this has been pushed or will be pushed soon? It looks >>>>>>>> like we're facing the same issue. >>>>>>>> >>>>>>>> On Wednesday, June 25, 2014 6:06:26 PM UTC-5, David Trowbridge >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> This particular issue in rbtools is already fixed in Git and will >>>>>>>>> ship with the next release. We'll try to get that release out soon. >>>>>>>>> >>>>>>>>> -David >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Jun 25, 2014 at 1:17 PM, Neeraj K <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi all, >>>>>>>>>> >>>>>>>>>> I am using RBTools 0.6.1. While posting reviews I get this error >>>>>>>>>> >>>>>>>>>> techopss-mbp-10:minted neeraj$ rbt post -g >>>>>>>>>> --target-groups=fulfillment -d -r23696 >>>>>>>>>> >>>>>>>>>> >>> RBTools 0.6.1 >>>>>>>>>> >>>>>>>>>> >>> Python 2.7.5 (default, Aug 25 2013, 00:04:04) >>>>>>>>>> >>>>>>>>>> [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] >>>>>>>>>> >>>>>>>>>> >>> Running on Darwin-13.1.0-x86_64-i386-64bit >>>>>>>>>> >>>>>>>>>> >>> Home = /Users/neeraj >>>>>>>>>> >>>>>>>>>> >>> Current directory = /Users/neeraj/Work/Minted/minted >>>>>>>>>> >>>>>>>>>> >>> Checking for a Subversion repository... >>>>>>>>>> >>>>>>>>>> >>> Running: svn info --non-interactive >>>>>>>>>> >>>>>>>>>> >>> Command exited with rc 1: ['svn', 'info', '--non-interactive'] >>>>>>>>>> >>>>>>>>>> svn: E155007: '/Users/neeraj/Work/Minted/minted' is not a >>>>>>>>>> working copy >>>>>>>>>> >>>>>>>>>> --- >>>>>>>>>> >>>>>>>>>> >>> Checking for a Git repository... >>>>>>>>>> >>>>>>>>>> >>> Running: git rev-parse --git-dir >>>>>>>>>> >>>>>>>>>> >>> Running: git config core.bare >>>>>>>>>> >>>>>>>>>> >>> Running: git rev-parse --show-toplevel >>>>>>>>>> >>>>>>>>>> >>> Running: git symbolic-ref -q HEAD >>>>>>>>>> >>>>>>>>>> >>> Running: git svn info >>>>>>>>>> >>>>>>>>>> >>> repository info: Path: https://svn.minted.com/svn, Base >>>>>>>>>> path: /minted/branches/release-printerapi, Supports changesets: >>>>>>>>>> False >>>>>>>>>> >>>>>>>>>> >>> Making HTTP GET request to https://reviewboard.minted.com >>>>>>>>>> /api/ >>>>>>>>>> >>>>>>>>>> >>> Running: git rev-parse refs/heads/relprinterapi2 >>>>>>>>>> >>>>>>>>>> >>> Running: git merge-base 5c06f64988aaeb6716d89e8e009582ca8c0f7b82 >>>>>>>>>> trunk >>>>>>>>>> >>>>>>>>>> >>> Running: git rev-parse e349309cd456b0b2a2265d2028d246 >>>>>>>>>> 8bb2325266 >>>>>>>>>> >>>>>>>>>> >>> Running: git status --porcelain --untracked-files=no >>>>>>>>>> >>>>>>>>>> >>> Running: git diff --no-color --no-prefix -r -u >>>>>>>>>> e349309cd456b0b2a2265d2028d2468bb2325266..5c06f64988aaeb6716 >>>>>>>>>> d89e8e009582ca8c0f7b82 >>>>>>>>>> >>>>>>>>>> >>> Running: git svn find-rev e349309cd456b0b2a2265d2028d246 >>>>>>>>>> 8bb2325266 >>>>>>>>>> >>>>>>>>>> >>> Running: git log --reverse --pretty=format:%s%n%n%b ^ >>>>>>>>>> e349309cd456b0b2a2265d2028d2468bb2325266 >>>>>>>>>> 5c06f64988aaeb6716d89e8e009582ca8c0f7b82 >>>>>>>>>> >>>>>>>>>> >>> Making HTTP GET request to https://reviewboard.minted.com >>>>>>>>>> /api/review-requests/23696/ >>>>>>>>>> >>>>>>>>>> >>> Making HTTP GET request to https://reviewboard.minted.com >>>>>>>>>> /api/review-requests/23696/diffs/ >>>>>>>>>> >>>>>>>>>> >>> Making HTTP POST request to https://reviewboard.minted.com >>>>>>>>>> /api/review-requests/23696/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'/minted/branches/release-printerapi/src/py/minted/logic/order/__init__.py', >>>>>>>>>> u'err': {u'msg': u'The file was not found in the repository.', >>>>>>>>>> u'code': >>>>>>>>>> 207}, u'revision': u'45974'} >>>>>>>>>> >>>>>>>>>> Traceback (most recent call last): >>>>>>>>>> >>>>>>>>>> File "/usr/local/bin/rbt", line 8, in <module> >>>>>>>>>> >>>>>>>>>> load_entry_point('RBTools==0.6.1', 'console_scripts', >>>>>>>>>> 'rbt')() >>>>>>>>>> >>>>>>>>>> File "/Library/Python/2.7/site-packages/RBTools-0.6.1-py2.7. >>>>>>>>>> egg/rbtools/commands/main.py", line 134, in main >>>>>>>>>> >>>>>>>>>> command.run_from_argv([RB_MAIN, command_name] + args) >>>>>>>>>> >>>>>>>>>> File "/Library/Python/2.7/site-packages/RBTools-0.6.1-py2.7. >>>>>>>>>> egg/rbtools/commands/__init__.py", line 416, in run_from_argv >>>>>>>>>> >>>>>>>>>> exit_code = self.main(*args) or 0 >>>>>>>>>> >>>>>>>>>> File "/Library/Python/2.7/site-packages/RBTools-0.6.1-py2.7. >>>>>>>>>> egg/rbtools/commands/post.py", line 784, in main >>>>>>>>>> >>>>>>>>>> submit_as=self.options.submit_as) >>>>>>>>>> >>>>>>>>>> File "/Library/Python/2.7/site-packages/RBTools-0.6.1-py2.7. >>>>>>>>>> egg/rbtools/commands/post.py", line 543, in post_request >>>>>>>>>> >>>>>>>>>> error_msg.append(e.decode('utf-8') + u'\n') >>>>>>>>>> >>>>>>>>>> AttributeError: 'BadRequestError' object has no attribute 'decode' >>>>>>>>>> >>>>>>>>>> Also when I create a separate branch and try I get the same >>>>>>>>>> error. It created these zombie reviews with nothing in them. I have >>>>>>>>>> tried >>>>>>>>>> this after discarding all such reviews but still get the same error. >>>>>>>>>> Any >>>>>>>>>> idea whats wrong ? >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> 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 [email protected]. >>>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>> 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 [email protected]. >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>>> -- >>>>>>> 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 [email protected]. >>>>>>> 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 [email protected]. >>>> 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 [email protected]. > 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
