2224: post-review fails w/ "error fetching extended information for this repository"

geneco*******@gmai***** (Google Code) (Is this you? Claim this profile.)
Jan. 22, 2014
What version are you running?
post-review --version : RBTools 0.3.2

What's the URL of the page containing the problem?
  Produce an svn diff w/ many files.

What steps will reproduce the problem?
  'svn diff' reports about 650 lines of diff spread over 11 files.
  I do:  post-review  (in top level); or  post-review --debug

What is the expected output? What do you see instead?
  It fails with:
... ['svn info' for each file, w/ 'svn info' msg repeated three times]
>>> svn info dmtcp/src/mtcpinterface.cpp
>>> svn info dmtcp/src/mtcpinterface.cpp
>>> svn info dmtcp/src/mtcpinterface.cpp
>>> HTTP GETting http://XXX.ccs.neu.edu/api/repositories/
>>> HTTP GETting http://XXX.ccs.neu.edu/api/repositories/1/
>>> HTTP GETting http://XXX.ccs.neu.edu/api/repositories/1/info/
>>> Got API Error 210 (HTTP code 500): There was an error fetching extended information for this repository
>>> Error data: {u'stat': u'fail', u'err': {u'msg': u'There was an error fetching extended information for this repository', u'code': 210}}
>>> Attempting to create review request on https://dmtcp.svn.sourceforge.net/svnroot/dmtcp for None
>>> HTTP POSTing to http://XXX.ccs.neu.edu/api/review-requests/: {'repository': 'https://dmtcp.svn.sourceforge.net/svnroot/dmtcp'}
>>> Got API Error 206 (HTTP code 400): The repository path specified is not in the list of known repositories
>>> Error data: {u'stat': u'fail', u'repository': u'https://dmtcp.svn.sourceforge.net/svnroot/dmtcp', u'err': {u'msg': u'The repository path specified is not in the list of known repositories', u'code': 206}}

What operating system are you using? What browser?
  Linux, no browser

Please provide any additional information below.
  The bug seems to be associated with a larger 'svn diff'.  Could it be a slow server?  Is there a way to force post-review to slow down and pause between each file?  Our DMTCP svn repository is at dmtcp.sf.net.  Our reviewboard setup is on a local machine at our site.  We don't have 'man post-review' here, but if you tell me where the config files for post-revew are, I can send them.
    (DMTCP is a package for transparent checkpointing, about 30,000 lines of code under svn.)
    Searching on "error fetching extended information for this repository" yields two other possibly related bugs:  Issue 1653 and Issue 2200.
david
#1 david
  • +Component-SCMTools
david
#2 david
It actually looks like this just needs a .reviewboardrc with REPOSITORY specified.
  • +SetupIssue
#6 imyua*****@gmai***** (Google Code) (Is this you? Claim this profile.)
I had the same problem. In fact, I had this very error when I ran `rbt setup-repo`. Anyways, I added my own .reviewboardrc manually. However, I can't seem to remove the error. Here are two screenshots of my setups, followed by an detailed exception thrown by running `rbt post d`.

Any help is appreciated.
#7 imyua*****@gmai***** (Google Code) (Is this you? Claim this profile.)
Some updates I found by tracking down the python exception in my previous comment:

`http GET http://192.168.0.152:8051/api` results in a 200 but `http://192.168.0.152:8051/api/repositories` results in a 404.

I attached the /api file downloaded by the browser here if it can be helpful.

When I created the reviewboard site, I ran `rb-site install /var/www/reviews.fht360.com` to create my site. I initially access my site by inserting `127.0.0.1  reviews.fht360.com` to the hosts file. Later on, I decided to make others in my team to access this by directly accessing via the ip address and port no. I also added the following to the settings_local.py:

     ALLOWED_HOSTS = ['reviews.fht360.com', 'localhost', '192.168.0.152'] 

Actually in my Reviewboard site, if I click [RBTools Setup] beside my repo, it will recommend me to add the following to the .reviewboardrc file:
     
     REVIEWBOARD_URL = 'http://reviews.fht360.com/'
     REPOSITORY = 'Test1'

I tried that also but it is not working.
  • +
    <?xml version="1.0" encoding="utf-8"?>
    <rsp>
     <stat>ok</stat>
     <uri_templates>
      <diff_comments>http://192.168.0.152:8051/api/review-requests/{review_request_id}/reviews/{review_id}/replies/{reply_id}/diff-comments/</diff_comments>
      <diff_validation>http://192.168.0.152:8051/api/validation/diffs/</diff_validation>
      <replies>http://192.168.0.152:8051/api/review-requests/{review_request_id}/reviews/{review_id}/replies/</replies>
      <watched_review_groups>http://192.168.0.152:8051/api/users/{username}/watched/review-groups/</watched_review_groups>
      <session>http://192.168.0.152:8051/api/session/</session>
      <file_attachments>http://192.168.0.152:8051/api/review-requests/{review_request_id}/file-attachments/</file_attachments>
      <file>http://192.168.0.152:8051/api/review-requests/{review_request_id}/diffs/{diff_revision}/files/{filediff_id}/</file>
      <diff>http://192.168.0.152:8051/api/review-requests/{review_request_id}/diffs/{diff_revision}/</diff>
      <watched>http://192.168.0.152:8051/
david
#8 david
Your 'rbt post -d' screenshot shows that it returned HTTP 500, which means something is wrong on the server side. Can you check the server logs (apache and reviewboard) and see what errors are in there? Please also include the review board version with your report.