Fantastic! Thanks, that works now.

--Jens

On Fri, Dec 9, 2016 at 11:29 AM, Pono Takamori <p...@apache.org> wrote:

> It was still using the old incubator-geode repo, so I've added the new
> named one.  Let me know if this helps.
>
> Cheers,
> -Pono
>
> On Fri, Dec 9, 2016 at 12:06 PM, Jens Deppe <jensde...@apache.org> wrote:
> > Hi,
> >
> > Our project, Geode, recently graduated to a TLP and now I am unable to
> post
> > a review to reviewboard. I'm getting this kind of error:
> >
> >
> > ± jd+am |feature/GEODE-2201 ✗| → rbt post -d --repository geode
> > --tracking-branch=origin/develop --target-groups=geode --server
> > https://reviews.apache.org
> >>>> RBTools 0.7.5
> >>>> Python 2.6.9 (unknown, Jul 30 2016, 18:31:01)
> > [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)]
> >>>> Running on Darwin-16.1.0-x86_64-i386-64bit
> >>>> Home = /Users/pivotal
> >>>> Current directory = /Users/pivotal/workspace/gemfire/open
> >>>> Checking for a Subversion repository...
> >>>> Running: svn --non-interactive info
> >>>> Command exited with rc 1: ['svn', '--non-interactive', u'info']
> > svn: E155007: '/Users/pivotal/workspace/gemfire/open' 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 config --get branch.feature/GEODE-2201.merge
> >>>> Running: git config --get branch.feature/GEODE-2201.remote
> >>>> Running: git config --get remote.origin.url
> >>>> repository info: Path:
> >>>> https://git-wip-us.apache.org/repos/asf/geode.git, Base path: ,
> Supports
> >>>> changesets: False
> >>>> Making HTTP GET request to https://reviews.apache.org/api/
> >>>> Running: git rev-parse refs/heads/feature/GEODE-2201
> >>>> Running: git merge-base d4276136337d2c9bee7336bafa281f2301af2a40
> >>>> origin/develop
> >>>> Running: git rev-parse 1d951e334334393c2052307988a21c1cd1f11985
> >>>> Running: git status --porcelain --untracked-files=no
> >>>> Running: git rev-parse --git-dir
> >>>> Running: git version
> >>>> Running: git -c core.quotepath=false -c diff.noprefix=false diff
> >>>> --no-color --full-index --ignore-submodules -M --no-ext-diff
> >>>> 1d951e334334393c2052307988a21c1cd1f11985..
> d4276136337d2c9bee7336bafa281f2301af2a40
> >>>> Making HTTP GET request to
> >>>> https://reviews.apache.org/api/validation/diffs/
> >>>> Cached response for HTTP GET
> >>>> https://reviews.apache.org/api/validation/diffs/ expired and was
> modified
> >>>> Making HTTP POST request to
> >>>> https://reviews.apache.org/api/validation/diffs/
> >>>> Got API Error 224 (HTTP code 400): The specified diff file could not
> be
> >>>> parsed.
> >>>> Error data: {u'stat': u'fail', u'reason': u'error: unable to find
> >>>> 91465f08f7a483cab0164f5d84dc8b0b8bdf780c\nfatal: git cat-file
> >>>> 91465f08f7a483cab0164f5d84dc8b0b8bdf780c: bad file\n', u'err':
> {u'msg':
> >>>> u'The specified diff file could not be parsed.', u'code': 224}}
> > Traceback (most recent call last):
> >   File "/usr/local/bin/rbt", line 9, in <module>
> >     load_entry_point('RBTools==0.7.5.dev0', 'console_scripts', 'rbt')()
> >   File "/Library/Python/2.6/site-packages/rbtools/commands/main.py",
> line
> > 133, in main
> >     command.run_from_argv([RB_MAIN, command_name] + args)
> >   File "/Library/Python/2.6/site-packages/rbtools/commands/__init__.py",
> > line 622, in run_from_argv
> >     exit_code = self.main(*args) or 0
> >   File "/Library/Python/2.6/site-packages/rbtools/commands/post.py",
> line
> > 754, in main
> >     (msg_prefix, e))
> > rbtools.commands.CommandError: Error validating diff
> >
> > The specified diff file could not be parsed. (HTTP 400, API Error 224)
> >
> >
> > However, in my repo the blob in question
> > (91465f08f7a483cab0164f5d84dc8b0b8bdf780c) does exist and was
> introduced in
> > commit 67dafd8 'GEODE-2112: UITests actually take screenshots on
> failure'.
> >
> > Does something need to be updated in reviewboard for our project?
> >
> > Thanks
> > --Jens
>

Reply via email to