sureshvv / reviewboard

Automatically exported from code.google.com/p/reviewboard
0 stars 0 forks source link

post-review does not handle error code 206 : The repository path specified is not in the list of known repositories #562

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
*NOTE: Do not post confidential information in this bug report.*

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

What steps will reproduce the problem?
1. setup review board with some subversion URL
2. use a different name for the repository URL in the checkout (ie. fully 
qualified host name)
3. try to submit a review

What is the expected output? What do you see instead?

I'm expecting a sane error message that lets me know what the problem might be. 
Instead I see 

Traceback (most recent call last):
  File "/usr/bin/pdb", line 1213, in main
    pdb._runscript(mainpyfile)
  File "/usr/bin/pdb", line 1138, in _runscript
    self.run(statement, globals=globals_, locals=locals_)
  File "/usr/lib/python2.5/bdb.py", line 366, in run
    exec cmd in globals, locals
  File "<string>", line 1, in <module>
  File "/home/cstejerean/bin/post-review", line 1561, in <module>
    main(sys.argv[1:])
  File "/home/cstejerean/bin/post-review", line 1543, in main
    submit_as=options.submit_as)
  File "/home/cstejerean/bin/post-review", line 1327, in tempt_fate
    review_request = server.new_review_request(changenum, submit_as)
  File "/home/cstejerean/bin/post-review", line 250, in new_review_request
    return rsp['review_request']
KeyError: 'review_request'

Please provide any additional information below.

Running under PDB I saw that rsp is {u'repository_path': 
u'svn+ssh://dev.leapfrogonline.com/vol2/svn', u'stat': u'fail', u'err': 
{u'msg': u'The repository 
path specified is not in the list of known repositories', u'code': 206}

Original issue reported on code.google.com by cstejer...@gmail.com on 30 Jul 2008 at 3:48

GoogleCodeExporter commented 9 years ago

Original comment by chip...@gmail.com on 25 Aug 2008 at 10:48

GoogleCodeExporter commented 9 years ago
I think this is fixed now. This error message shows up in a
slightly-more-human-readable way.

Original comment by trowb...@gmail.com on 21 Sep 2008 at 1:31