Re: API Error 224 - The specified diff file could not be parsed.

xact same error. > Ubuntu 16.04 > RBT 0.7.7 > RB 2.5.2 > > It's an unfixed bug in RB > > >>> 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 >

Re: API Error 224 - The specified diff file could not be parsed.

I'm getting the exact same error. Ubuntu 16.04 RBT 0.7.7 RB 2.5.2 It's an unfixed bug in RB >>> 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 b6387b56c32cbbc8e0731a

Re: The specified diff file could not be parsed.

t;>> Making HTTP GET request to http://codereview/api/validation/ > >>> Cached response for HTTP GET http://codereview/api/validation/ > expired and was not modified > >>> Making HTTP GET request to http://codereview/api/validation/diffs/ > >>> Cach

API Error 224 - The specified diff file could not be parsed.

nore-submodules -M --no-ext-diff 156168eb97cd9d4bc0eff74d70e68438e81aa8c9..525bf401c19ea8da6872fe3c39cadd56084dae07 >>> Making HTTP GET request to ***/validation/diffs/ >>> Cached response for HTTP GET */validation/diffs/ expired and was modified >>> Making HTTP POST

Re: Error: The specified diff file could not be parsed

The actual error is buried in there: Authentication failed when talking to the Subversion repository What this means is that the SVN repository configured in the Review Board admin page doesn't have the correct credentials. -David -- Supercharge your Review Board with Power Pack:

Error: The specified diff file could not be parsed

://192.168.180.33/api/validation/diffs/ expired and was modified Making HTTP POST request to http://192.168.180.33/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'Authentication failed when talking

Re: The specified diff file could not be parsed.

Hi Liam, This sounds like you're proxy server is being used for requests to your internal Review Board, which the proxy server is failing to access properly. I'm on the road so I can't give you exact details, but there's a command line option and configuration flag for telling RBTools to skip

Re: The specified diff file could not be parsed.

liam.r...@gmail.com Date: February 13, 2015 at 3:40:54 PM To: revie...@googlegroups.com revie...@googlegroups.com Cc: liam.r...@gmail.com liam.r...@gmail.com, chri...@beanbaginc.com chri...@beanbaginc.com Subject: Re: The specified diff file could not be parsed. Ah, I just

Re: The specified diff file could not be parsed.

After fiddling with this some more, I ended up discarding the repo config and creating a new config as a Gitlab repo. This seems to have worked, however, when I try to post a review: 08:03 $ rbt post -g yes --bugs-closed 19788098 -d RBTools 0.7.1 Python 2.6.9 (unknown, Sep 9 2014, 15:05:12)

Re: The specified diff file could not be parsed.

After fiddling with this some more, I ended up discarding the repo config and creating a new config as a Gitlab repo. This seems to have worked, however, when I try to post a review: 08:03 $ rbt post -g yes --bugs-closed 19788098 -d RBTools 0.7.1 Python 2.6.9 (unknown, Sep 9 2014, 15:05:12)

Re: The specified diff file could not be parsed.

To: revie...@googlegroups.com javascript: revie...@googlegroups.com javascript: Cc: liam.r...@gmail.com javascript: liam.r...@gmail.com javascript:, chri...@beanbaginc.com javascript: chri...@beanbaginc.com javascript: Subject: Re: The specified diff file could not be parsed. Ah, I

Re: The specified diff file could not be parsed.

liam.r...@gmail.com, chri...@beanbaginc.com chri...@beanbaginc.com Subject: Re: The specified diff file could not be parsed. Ah, I just saw part of your error: Not a git repository: 'None.' How is your repository configured in Review Board? Name - Repository

Re: The specified diff file could not be parsed.

Subject: Re: The specified diff file could not be parsed. Ah, I just saw part of your error: Not a git repository: 'None.' How is your repository configured in Review Board? Name - Repository Hosting - None (custom) Type - Git Path - git@server:path

Re: The specified diff file could not be parsed.

...@beanbaginc.com Subject:  Re: The specified diff file could not be parsed. Ah, I just saw part of your error: Not a git repository: 'None.' How is your repository configured in Review Board? Name - Repository Hosting - None (custom) Type - Git Path - git@server:path/repo.git

Re: The specified diff file could not be parsed.

I should also note that HEAD is a modification of an existing file, and HEAD~1 was adding a new file. Sort of reminds me of: https://groups.google.com/forum/#!topic/reviewboard/U-pVdasCWxw However, I don't get the error in that thread. -- Supercharge your Review Board with Power Pack:

Re: The specified diff file could not be parsed.

://reviewboard/api/validation/diffs/ Making HTTP POST request to http://reviewboard/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': ufatal: Not a git repository: 'None'\n, u'err': {u'msg': u'The specified diff

Re: The specified diff file could not be parsed.

Is there a way to see what diff is being posted by the tool? -- 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/

Re: The specified diff file could not be parsed.

AM To: reviewboard@googlegroups.com reviewboard@googlegroups.com Subject:  Re: The specified diff file could not be parsed. I should also note that HEAD is a modification of an existing file, and HEAD~1 was adding a new file. Sort of reminds me of: https://groups.google.com/forum/#!topic

Re: The specified diff file could not be parsed.

': ufatal: Not a git repository: 'None'\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 8, in module load_entry_point('RBTools==0.7.1.dev', 'console_scripts', 'rbt')() File /Library/Python/2.6

Re: The specified diff file could not be parsed.

: The specified diff file could not be parsed. Does the problem go away if the local branch is rebased back onto master again? No, it does not. I checkout out master, merged the branch (single change), and ran: rbt post -g yes --bugs-closed 19788098 -d It had the same output

Re: The specified diff file could not be parsed.

Ah, I just saw part of your error: Not a git repository: 'None.' How is your repository configured in Review Board? Name - Repository Hosting - None (custom) Type - Git Path - git@server:path/repo.git However, note that the client can post a review request using one invocation (with

Re: The specified diff file could not be parsed.

Would it be possible for you to test with the just-released 2.0.13? We've improved several aspects of parsing git diffs. -David On Thu Feb 12 2015 at 4:11:53 PM Liam Reimers liam.reim...@gmail.com wrote: I'm having this exact issue as well. Is there any additional information I can post to

Re: The specified diff file could not be parsed.

I'm having this exact issue as well. Is there any additional information I can post to help troubleshoot? RBTools 0.7.1 Python 2.6.9 (unknown, Sep 9 2014, 15:05:12) -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for

The specified diff file could not be parsed.

://codereview/api/validation/diffs/ Cached response for HTTP GET http://codereview/api/validation/diffs/ expired and was modified Making HTTP POST request to http://codereview/api/validation/diffs/ Got API Error 224 (HTTP code 400): The specified diff file could not be parsed. Error data: {u'stat