RBTools: 1.0.1
RBCommons 3.0.12

Sometime in the last couple of days, every attempt at  generating a review 
request via "rbt post" results in an "API Error 207...File not found in 
repository" error.  This happens for every person on our team, and has 
basically stopped our review process. 

I ran some tests with a small change and used the --debug option to attempt 
to figure out what was happening (Attached below). 

I ran each of the git commands by hand, and all worked as expected. The 
diff is created, but the error message contains a SHA value that doesn't 
exist in the repository, which I'm guessing results in the error, but I 
can't figure out where that value is coming from. 

Any help on where I look next would be greatly appreciated!

Rod




rbt post --debug upstream/pcg_3.0.x..origin/top-gear-fuel
>>> RBTools 1.0.1
>>> Python 2.7.6 (default, Nov 13 2018, 12:45:42) 
[GCC 4.8.4]
>>> Running on Linux-4.4.0-142-generic-x86_64-with-Ubuntu-14.04-trusty
>>> Home = /home/rflancher
>>> Current directory = <repository-base redacted>
>>> Command line: rbt post --debug upstream/pcg_3.0.x..origin/top-gear-fuel
>>> Running: tf vc help
>>> 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.top-gear-fuel.merge
>>> Command exited with rc 1: [u'git', u'config', u'--get', 
u'branch.top-gear-fuel.merge']
---
>>> Running: git config --get branch.top-gear-fuel.remote
>>> Command exited with rc 1: [u'git', u'config', u'--get', 
u'branch.top-gear-fuel.remote']
---
>>> Running: git config --get remote.origin.url
>>> Repository info: Path: <repository-redacted> Base path: , Supports 
changesets: False
>>> Making HTTP GET request to https://rbcommons.com/s/<redacted>/api/
>>> Running: git rev-parse upstream/pcg_3.0.x..origin/top-gear-fuel
>>> Running: git rev-list 458d6dabeb49f8e60609ba17b1b4674f128e2803 --not 
--remotes=origin
>>> Running: git version
>>> Running: git -c core.quotepath=false -c diff.noprefix=false diff 
--no-color --full-index --ignore-submodules -M --no-ext-diff 
458d6dabeb49f8e60609ba17b1b4674f128e2803..36c35ec0c358413067cdd2e36b19b41aa5e64ea6
>>> Generated diff size: 443 bytes
>>> Making HTTP GET request to 
https://rbcommons.com/s/<redacted>api/validation/diffs/
>>> Cached response for HTTP GET 
https://rbcommons.com/s/<redacted>/api/validation/diffs/ expired and was 
modified
>>> Making HTTP POST request to 
https://rbcommons.com/s/<redacted>/api/validation/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'apps/vehicle/vehicle.c', 
u'err': {u'msg': u'The file was not found in the repository.', u'code': 
207}, u'revision': u'9000d87296b83efd04236026ba2a20ae60707a5c'}
Traceback (most recent call last):
  File "/usr/local/bin/rbt", line 9, in <module>
    load_entry_point('RBTools==1.0.1', 'console_scripts', 'rbt')()
  File 
"/usr/local/lib/python2.7/dist-packages/RBTools-1.0.1-py2.7.egg/rbtools/commands/main.py",
 
line 120, in main
    command.run_from_argv([RB_MAIN, command_name] + args)
  File 
"/usr/local/lib/python2.7/dist-packages/RBTools-1.0.1-py2.7.egg/rbtools/commands/__init__.py",
 
line 719, in run_from_argv
    exit_code = self.main(*args) or 0
  File 
"/usr/local/lib/python2.7/dist-packages/RBTools-1.0.1-py2.7.egg/rbtools/commands/post.py",
 
line 875, in main
    (msg_prefix, e))
rbtools.commands.CommandError: Error validating diff

apps/vehicle/vehicle.c: The file was not found in the repository. (HTTP 
400, API Error 207)

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" 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.

Reply via email to