I'm seeing a "The file was not found in the repository" error against a Git server but don't know why...

[eric via reviewboard]

Very confused. Perhaps this is fixed by an upgrade? I'm running 2.5.9.

I've got a user who clones a Git repository, makes a random change to the 
source, commits the change, then tries "rbt post -d". It fails. I've been 
able to reproduce the problem, so it isn't restricted to the specific user.

(Note that I've blanked details specific to our environment, that seem 
unrelated to the bug.)

>>> RBTools 0.7.10
>>> Python 2.7.10 (default, Feb  7 2017, 00:08:15) 
___
>>> Command line: rbt post -d
>>> Running: tf vc help
>>> Checking for a Subversion repository...
>>> Running: svn --non-interactive info
>>> Command exited with rc 1: ['svn', '--non-interactive', u'info']
svn: E155007: '___' 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.master.merge
>>> Running: git config --get branch.master.remote
>>> Running: git config --get remote.origin.url
>>> repository info: Path: https://__, Base path: , 
Supports changesets: False
>>> Making HTTP GET request to https://___api/
>>> Running: git rev-parse refs/heads/master
>>> Running: git merge-base e7b4515500eddbacd3846f24e59e6b5c5672fa6b 
origin/master
>>> Running: git rev-parse 0c5abaf3d4854a4e13f084b85aa7bb9f3b8c491e
>>> Running: git status --porcelain --untracked-files=no 
--ignore-submodules=dirty
>>> 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 
0c5abaf3d4854a4e13f084b85aa7bb9f3b8c491e..e7b4515500eddbacd3846f24e59e6b5c5672fa6b
>>> Making HTTP GET request to 
https://__api/validation/diffs/
>>> Cached response for HTTP GET 
https://api/validation/diffs/ expired and was modified
>>> Making HTTP POST request to 
https://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'karma.conf.js', u'err': 
{u'msg': u'The file was not found in the repository.', u'code': 207}, 
u'revision': u'3c350734aaf218bc5d8c2b5ee1e257ff22ac2e7d'}
Traceback (most recent call last):
  File "/usr/local/bin/rbt", line 9, in 
load_entry_point('RBTools==0.7.10', 'console_scripts', 'rbt')()
  File 
"/Library/Python/2.7/site-packages/RBTools-0.7.10-py2.7.egg/rbtools/commands/main.py",
 
line 133, in main
command.run_from_argv([RB_MAIN, command_name] + args)
  File 
"/Library/Python/2.7/site-packages/RBTools-0.7.10-py2.7.egg/rbtools/commands/__init__.py",
 
line 663, in run_from_argv
exit_code = self.main(*args) or 0
  File 
"/Library/Python/2.7/site-packages/RBTools-0.7.10-py2.7.egg/rbtools/commands/post.py",
 
line 812, in main
(msg_prefix, e))
rbtools.commands.CommandError: Error validating diff

What's going on, and how do I fix it?

Eric


-- 
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 
"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.

Re: Review Board Ticket #4450: ReviewRequest.last_review_activity_timestamp should be exposed in the API

[Kevin Yu]

--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4450/
--

New update by samsun387
For Beanbag, Inc. > Review Board > Ticket #4450


Reply:

Hi,

Just following up on this. Since it's marked as an easy fix, is there a 
targetted release for it at the moment?

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.

Review Board Ticket #4559: Some keyboard shortcuts are broken in 2.5.12 and above

[Tyler Wright]

--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4559/
--

New ticket #4559 by tylwright
For Beanbag, Inc. > Review Board

Status: New
Tags: Priority:Medium, Type:Defect


--
Some keyboard shortcuts are broken in 2.5.12 and above
==

# What version are you running?
2.5.12

# What's the URL of the page containing the problem?
Private

# What steps will reproduce the problem?
1. Navigate to a review
2. Click on diff
3. Type any of the following:
Previous file: a, A, K, P:, <, or m
Next file: f, F, J, N, >


# What is the expected output? What do you see instead?
Should move to the next or previous file depending on which key you press

# What operating system are you using? What browser?
Windows 10 - Chrome 58.0.3029.110 and Internet Explorer

# Please provide any additional information below.
Was working prior to us upgrading to 2.5.12 (was on early 2.5.x).  
http://reviews.reviewboard.org also seems to have this issue.

--

-- 
You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at https://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.

Re:

[Stephen Gallagher]

On Fri, Jun 23, 2017 at 7:51 AM Shilpa R  wrote:

> Hi,
>
> I have python version 2.7 on the same Centos machine 5.x :-
>
>  python -V
> Python 2.7.10
>
> is it not compatible with RBTools?
>
>
In that case, I advise you to do:

`yum remove RBTools`
followed by
`pip install RBTools`

That *should* get you what you need. Though I can't promise that it will
work perfectly, since as I mentioned, CentOS 5 is past its end-of-life.
(Which means that if any of the dependencies like pysvn are too old, you
may be out of luck)

-- 
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 
"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.

Re:

[Shilpa R]

Hi,

I have python version 2.7 on the same Centos machine 5.x :-

 python -V
Python 2.7.10

is it not compatible with RBTools?


On Thursday, June 22, 2017 at 3:18:18 AM UTC+5:30, Christian Hammond wrote:
>
> It's also worth noting that the next major version of RBTools will be 
> dropping Python 2.6 support.
>
> Christian
>
> On Wed, Jun 21, 2017 at 1:24 PM, Stephen Gallagher <
> ste...@gallagherhome.com > wrote:
>
>> On Wed, Jun 21, 2017 at 2:40 AM Shilpa R > > wrote:
>>
>>> Ok.
>>>
>>> Actually I have machines which are Centos 5/6/7. And I will need Centos 
>>> 5 support also for posting review requests on Review board Server.
>>>
>>> So on Centos 6 I have successfully connected to ReviewBoard Server with 
>>> the help of 0.7 version RBTools.
>>>
>>> But whereas on Centos 5 I have installed 0.5 version RBTools and I am 
>>> facing the below issue :-
>>>
>>> *rbt post -d*
>>> ERROR:root:Could not load SCM Client "svn": No module named etree
>>> ERROR:root:Could not load SCM Client "git": No module named etree
>>> ERROR:root:Could not load SCM Client "mercurial": No module named etree
>>> DEBUG:root:Checking for a ClearCase repository...
>>> DEBUG:root:Checking for a Bazaar repository...
>>> DEBUG:root:Checking for a CVS repository...
>>> DEBUG:root:Checking for a Perforce repository...
>>> DEBUG:root:Checking for a Plastic repository...
>>> ERROR:root:No supported repository could be accessed at the supplied url.
>>>
>>> The configuration are same as Centos 6 which executes correctly. I think 
>>> on Centos 5 it is unable to connect to the repository.
>>>
>>> The *.reviewboardrc* configurations are:-
>>>
>>> REVIEWBOARD_URL = "172.16.107.138"
>>> REPOSITORY = "XXX"
>>>
>>>
>>> What might be  the issue?
>>>
>>> Regards
>>> Shilpa
>>>
>>>
>>
>> If you really must run RBTools on a CentOS 5 host, your best bet would be 
>> to:
>> 1) Remove the RBTools RPM (`yum remove RBTools`)
>> 2) Install the 'python26' package from EPEL 5 (`yum install python26`)
>>
>> Then you'll need to install 'pip' from PyPI for python 2.6 and then `pip 
>> install RBTools`
>>
>> -- 
>> 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 
>> "reviewboard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Christian Hammond
> President/CEO of Beanbag 
> Makers of Review Board 
>

-- 
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 
"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.

Re: rbt post for Git yields "The file was not found in the repository. (HTTP 400, API Error 207)"

[Christian Hammond]

Hi Nick,

We'll fix the upgrade instructions. The proper method really does depend on
the system, though (pip is the worst option on older installs, but the best
option on newer ones).

The recent 2.5.13 releases added new information and solutions for version
mismatch problems, so if this happens in the future (going from 2.5.13+ to
some newer version), you'll receive the instructions. (Nothing we can do
about upgrading from older versions to 2.5.13, since the new code isn't
running in this case.)

Christian

On Fri, Jun 23, 2017 at 12:04 AM, Nick Pruehs 
wrote:

> Hey Christian, hey Stephen,
>
> thanks again for your quick responses. With these, Paul, one of our more
> experienced IT experts, found and resolved the issue. It was due to a
> parallel installation of the pip and the easy_install versions, indeed.
>
> I've got a little feedback for you guys in order to avoid similar future
> support requests:
>
>1. Add a more distinguished upgrade error message. In the above
>example, the error message (correctly) states: "The version of Review Board
>running does not match the version the site was last upgraded to. You are
>running *2.5.11* and the site was last upgraded to *2.5.13.1*." In
>fact, I misread it, assuming that it would be the other way round, namely
>the web application being newer than the site. This was, in part, caused by
>the following sentence, suggesting to upgrade the site: "Please upgrade
>your site to fix this by running: ..." Maybe you could show a different
>suggestion in this case.
>2. Update either your installation guide or your update guide to
>match: The default installation guide for Linux
>
> 
>suggests installing the application with pip, whereas the upgrade guide
>
> 
>suggests updating it with easy_install.
>
> Thanks again for your help,
> Nick
>
>
>
> On Thursday, June 22, 2017 at 9:46:50 PM UTC+2, Stephen Gallagher wrote:
>
>> Given that you have 2.5.11, which is the version that was stable repo for
>> EPEL until today, I am guessing you have the RPMs and suspect you will want
>> to do "yum update ReviewBoard --enablerepo=updates-testing" and get a copy
>> of 2.5.13.1
>>
>> (Note it just went into the EPEL testing repo today, so it might take up
>> to 24 hours to hit your closest mirror)
>> On Thu, Jun 22, 2017 at 3:36 PM Christian Hammond 
>> wrote:
>>
>>> Hi Nick,
>>>
>>> Most likely you installed the previous version using a different
>>> installation method (pip or yum) than you used this time (easy_install?)
>>> and the old package is taking precedence. Check
>>> /usr/lib/python2.7/site-packages/ for all ReviewBoard* entries and show
>>> me what you've found.
>>>
>>> Christian
>>>
>>>
>>> On Thu, Jun 22, 2017 at 08:15 Nick Pruehs  wrote:
>>>
 Hey Christian!

 Thanks for the advice. I've followed the instructions at


- https://www.reviewboard.org/docs/manual/dev/admin/upgrading/
upgrading-reviewboard/
- https://www.reviewboard.org/docs/manual/dev/admin/upgrading/
upgrading-sites/

 The application upgrade seems to be successful, however, the site
 update not. The console output is as follows:

 root@tegan:/var/www# rb-site upgrade /var/www/reviewboard
 Rebuilding directory structure
 Upgrading site settings_local.py
 Updating database. This may take a while.
 The log output below, including warnings and errors,
 can be ignored unless upgrade fails.
 --  --
 Creating tables ...
 Installing custom SQL ...
 Installing indexes ...
 Installed 0 object(s) from 0 fixture(s)
 No evolution required.
 ---  ---
 Resetting in-database caches.
 Upgrade complete!

 However, after restarting both Apache and Memcached, we're still facing
 the required update message:


 Manual server updates required

 A recent upgrade requires manual updates to be made on this server.
 After these changes are made, you should restart your web server.

 If you have any questions or problems, please contact us on our *mailing
 list* .
 Review Board version mismatch

 The version of Review Board running does not match the version the site
 was last upgraded to. You are running *2.5.11* and the site was last
 upgraded to *2.5.13.1*.

 Please upgrade your site to fix this by running:

 $ rb-site upgrade /var/www/reviewboard



 Are we still missing something?

 Warm regards,
 Nick


 On Thursday, June 22, 2017 at 

Re: rbt post for Git yields "The file was not found in the repository. (HTTP 400, API Error 207)"

[Nick Pruehs]

Hey Christian, hey Stephen,

thanks again for your quick responses. With these, Paul, one of our more 
experienced IT experts, found and resolved the issue. It was due to a 
parallel installation of the pip and the easy_install versions, indeed.

I've got a little feedback for you guys in order to avoid similar future 
support requests:

   1. Add a more distinguished upgrade error message. In the above example, 
   the error message (correctly) states: "The version of Review Board running 
   does not match the version the site was last upgraded to. You are running 
   *2.5.11* and the site was last upgraded to *2.5.13.1*." In fact, I 
   misread it, assuming that it would be the other way round, namely the web 
   application being newer than the site. This was, in part, caused by the 
   following sentence, suggesting to upgrade the site: "Please upgrade your 
   site to fix this by running: ..." Maybe you could show a different 
   suggestion in this case.
   2. Update either your installation guide or your update guide to match: 
   The default installation guide for Linux 
   

 
   suggests installing the application with pip, whereas the upgrade guide 
   

 
   suggests updating it with easy_install.

Thanks again for your help,
Nick



On Thursday, June 22, 2017 at 9:46:50 PM UTC+2, Stephen Gallagher wrote:

> Given that you have 2.5.11, which is the version that was stable repo for 
> EPEL until today, I am guessing you have the RPMs and suspect you will want 
> to do "yum update ReviewBoard --enablerepo=updates-testing" and get a copy 
> of 2.5.13.1
>
> (Note it just went into the EPEL testing repo today, so it might take up 
> to 24 hours to hit your closest mirror)
> On Thu, Jun 22, 2017 at 3:36 PM Christian Hammond  > wrote:
>
>> Hi Nick,
>>
>> Most likely you installed the previous version using a different 
>> installation method (pip or yum) than you used this time (easy_install?) 
>> and the old package is taking precedence. Check 
>> /usr/lib/python2.7/site-packages/ for all ReviewBoard* entries and show me 
>> what you've found.
>>
>> Christian
>>
>>
>> On Thu, Jun 22, 2017 at 08:15 Nick Pruehs > > wrote:
>>
>>> Hey Christian!
>>>
>>> Thanks for the advice. I've followed the instructions at
>>>
>>>
>>>- 
>>>
>>> https://www.reviewboard.org/docs/manual/dev/admin/upgrading/upgrading-reviewboard/
>>>- 
>>>
>>> https://www.reviewboard.org/docs/manual/dev/admin/upgrading/upgrading-sites/
>>>
>>> The application upgrade seems to be successful, however, the site update 
>>> not. The console output is as follows:
>>>
>>> root@tegan:/var/www# rb-site upgrade /var/www/reviewboard
>>> Rebuilding directory structure
>>> Upgrading site settings_local.py
>>> Updating database. This may take a while.
>>> The log output below, including warnings and errors,
>>> can be ignored unless upgrade fails.
>>> --  --
>>> Creating tables ...
>>> Installing custom SQL ...
>>> Installing indexes ...
>>> Installed 0 object(s) from 0 fixture(s)
>>> No evolution required.
>>> ---  ---
>>> Resetting in-database caches.
>>> Upgrade complete!
>>>
>>> However, after restarting both Apache and Memcached, we're still facing 
>>> the required update message:
>>>
>>>
>>> Manual server updates required
>>>
>>> A recent upgrade requires manual updates to be made on this server. 
>>> After these changes are made, you should restart your web server. 
>>>
>>> If you have any questions or problems, please contact us on our *mailing 
>>> list* . 
>>> Review Board version mismatch
>>>
>>> The version of Review Board running does not match the version the site 
>>> was last upgraded to. You are running *2.5.11* and the site was last 
>>> upgraded to *2.5.13.1*. 
>>>
>>> Please upgrade your site to fix this by running: 
>>>
>>> $ rb-site upgrade /var/www/reviewboard
>>>
>>>
>>>
>>> Are we still missing something?
>>>
>>> Warm regards,
>>> Nick
>>>
>>>
>>> On Thursday, June 22, 2017 at 12:47:22 PM UTC+2, Christian Hammond wrote:
>>>
 Hi Nick,

 Your original configuration was correct (and required -- the second one 
 won't work).

 The problem you're hitting was fixed in Review Board 2.0.12. The 2.0.11 
 release, which was very short-lived, regressed new configs for GitHub. I'd 
 strongly recommend getting the very latest though (2.0.13.1), as it 
 contains security fixes.

 Christian



 On Thu, Jun 22, 2017 at 03:25 Nick Pruehs  
 wrote:

>>> Hi all,
>
> we are trying to generate a review request for a public Git repository:
>
>