post-review w/ p4 error: Got API Error 105 (HTTP code 200): One or more fields had errors
trying to setup post-review with perforce got the following error.
I am able to ping and telnet to the perforce server from my
client my repository setting is:
Hosting service: Custom
Repository type: Perforce
Path: perforce.example.com
Username: useranme
Password: password
$ post-review --debug --summary=p4-testing-change
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.example.com:1666, Base path: None, Supports
changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to /tmp/tmpzT7Exi
p4 print -o /tmp/tmpzT7Exi -q //depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpzT7Exi
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated 1.0
API
== Review Board Login Required
Enter username and password for Review Board at
http://vmreviews.lab-example.com/reviews/
Looking for 'vmreviews.lab-example /reviews/' cookie in
/home/build/.post-review-cookies.txt
Loaded valid cookie -- no login required
Attempting to create review request on perforce.example.com for None
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/new/:
{'repository_path': 'perforce.example.com'}
Review request created
Attempting to set field 'summary' to 'p4-testing-change' for review request
'12'
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/draft/set/:
{'summary': 'p4-testing-change'}
Uploading diff, size: 361
HTTP POSTing to
http://vmreviews.lab-example.com/reviews/api/json/reviewrequests/12/diff/new/:
{}
Got API Error 105 (HTTP code 200): One or more fields had errors
Error data: {u'fields': {u'path': [u'[P4.connect()] Connect to server
failed; check $P4PORT.\nTCP connect to perforce.example.com
failed.\nperforce.example.com: service unknown.\n']}, u'stat': u'fail',
u'err': {u'msg': u'One or more fields had errors', u'code': 105},
u'deprecated': {u'in_version': u'1.5'}}
Error uploading diff
The generated diff file was empty. This usually means no files were
modified in this change.
Try running with --output-diff and --debug for more information.
Your review request still exists, but the diff is not attached.
$ post-review --debug --summary=p4-testing-change --output-diff
RBTools 0.3.2
Home = /home/build
svn info
p4 info
repository info: Path: repoman.example.com:1666, Base path: None, Supports
changesets: True
HTTP GETting api/
HTTP GETting http://vmreviews.lab-example.com/reviews/api/info/
Using the new web API
Generating diff for changenum default
p4 opened -c default
Processing edit of //depot/Iocaine/main/Product/build.xml
Writing //depot/Iocaine/main/Product/build.xml#197 to /tmp/tmpDCtOBl
p4 print -o /tmp/tmpDCtOBl -q //depot/Iocaine/main/Product/build.xml#197
diff -urNp /tmp/tmpDCtOBl
/home/build/build_client/Iocaine/main/Product/build.xml
Using changenums on Review Board 1.5.2. Falling back to the deprecated 1.0
API
--- //depot/Iocaine/main/Product/build.xml //depot/Iocaine/main/
Product/build.xml#197
+++ //depot/Iocaine/main/Product/build.xml 2011-03-30 06:09:25
@@ -1,4 +1,5 @@
project name=Iocaine default=all-nodist basedir=.
+project name=Iocaine default=all-nodist basedir=.
property environment=env /
property name=src_dir value=src/ /
$
what does check $P4PORT.\nTCP connect to perforce.example.com
failed. mean?
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
post-review: Unable to find a Review Board server for this source code tree
Just installed RBTools on my 1.5.5 RedHat server where Reviewboard is installed, and this is first time installing RBTools with the following command: easy_install -U RBTools # which post-review /usr/bin/post-review I am getting the following error when trying to use it with CVS # post-review --debug --username=username --password=passwd Build RBTools 0.3.2 Home = /root svn info repository info: Path: fully-qualified-hostname:/cvs, Base path: None, Supports changesets: False Unable to find a Review Board server for this source code tree. My cvs repository setting is as follows: Hosting service: custom Repository type: CVS Path: :pserver:username:password@fully-qualified-hostname:/cvs Mirror path: blank Username: usrname password: passowrd Is there something I missed during the install, which path is it looking for? thx -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: post-review: Unable to find a Review Board server for this source code tree
I now have .reviewboardrc in my home diretory with the following:
REPOSITORY = cvs.x.com:/cvs
REVIEWBOARD_URL = http://vmreviews.lab.x.com/reviews/;
My cvs repository setting is as follows:
Hosting service: custom
Repository type: CVS
Path: :pserver:username:password@cvs.x.com:/cvs
Mirror path: blank
Username: usrname
password: passowrd
I get the following 206 error running post-review:
$ post-review --debug Build
RBTools 0.3.2
Home = /home/userx
svn info
repository info: Path: repoman.s.x.com:/cvs, Base path: None, Supports
changesets: False
HTTP GETting api/
HTTP GETting http://vmreviews.lab.x.com/reviews/api/info/
Using the new web API
cvs diff -uN Build
Attempting to create review request on cvs.x.com:/cvs for None
HTTP POSTing to http://vmreviews.lab.x.com/reviews/api/review-requests/:
{'repository': 'cvs.x.com:/cvs'}
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'cvs.x.com:/cvs', u'err':
{u'msg': u'The repository path specified is not in the list of known
repositories', u'code': 206}}
There was an error creating this review request.
The repository path repoman.s.x.com:/cvs is not in the list of known
repositories on the server.
Ask the administrator to add this repository to the Review Board
server.
For information on adding repositories, please read
http://www.reviewboard.org/docs/manual/dev/admin/management/repositories/
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
LDAP setup with 1.5.4
I am trying to setup LDAP on my new install with 1.5.4 on RedHat using apache + mod_python. I can't seem to get it to work... Here's my latest from the /var/log/httpd/error_log... I see the warning messages but not sure how to proceed with them... I have defined the following in Authentication Settings page: LDAP Server: ldap://server:389 LDAP BaseDN: dc=sendmail,dc=com User Mask: ((objectClass=User) (mailNickname=%s)) [Fri Mar 25 09:12:32 2011] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads. [Fri Mar 25 09:12:32 2011] [notice] Apache/2.2.3 (Red Hat) configured -- resuming normal operations /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/ __init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated; use settings.DATABASES instead. DeprecationWarning /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/ __init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.' DeprecationWarning /usr/lib/python2.4/site-packages/pycrypto-2.3-py2.4-linux-i686.egg/ Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This application uses RandomPool, which is BROKEN in older releases. See http://www.pycrypto.org/randpool-broken /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/contrib/ auth/__init__.py:26: DeprecationWarning: Authentication backends without a `supports_object_permissions` attribute are deprecated. Please define it in class 'reviewboard.accounts.backends.LDAPBackend'. DeprecationWarning) /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/contrib/ auth/__init__.py:31: DeprecationWarning: Authentication backends without a `supports_anonymous_user` attribute are deprecated. Please define it in class 'reviewboard.accounts.backends.LDAPBackend'. DeprecationWarning) WARNING:root:LDAP error: The specified object does not exist in the Directory: ((objectClass=User) (mailNickname=admin)) -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
500 - Internal Server Error | Review Board
Just installed 1.5.4 with Apache + mod_python started apache, and try to access web and got the following and got the following error via browser: 500 - Internal Server Error | Review Board - Mozilla Firefox Something broke! (Error 500) It appears something broke when you tried to go to here. This is either a bug in Review Board or a server configuration error. Please report this to your administrator. here's the log file: [Thu Mar 24 17:10:53 2011] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Thu Mar 24 17:10:53 2011] [notice] Digest: generating secret for digest authentication ... [Thu Mar 24 17:10:53 2011] [notice] Digest: done [Thu Mar 24 17:10:53 2011] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads. [Thu Mar 24 17:10:53 2011] [notice] Apache/2.2.3 (Red Hat) configured -- resuming normal operations /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/ __init__.py:19: DeprecationWarning: settings.DATABASE_* is deprecated; use settings.DATABASES instead. DeprecationWarning /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/db/ __init__.py:60: DeprecationWarning: Short names for ENGINE in database configurations are deprecated. Prepend default.ENGINE with 'django.db.backends.' DeprecationWarning /usr/lib/python2.4/site-packages/pycrypto-2.3-py2.4-linux-i686.egg/ Crypto/Util/randpool.py:40: RandomPool_DeprecationWarning: This application uses RandomPool, which is BROKEN in older releases. See http://www.pycrypto.org/randpool-broken /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/core/ context_processors.py:27: DeprecationWarning: The context processor at `django.core.context_processors.auth` is deprecated; use the path `django.contrib.auth.context_processors.auth` instead. DeprecationWarning /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/template/ loaders/filesystem.py:58: DeprecationWarning: 'django.template.loaders.filesystem.load_template_source' is deprecated; use 'django.template.loaders.filesystem.Loader' instead. DeprecationWarning ERROR:root:Exception thrown for user AnonymousUser at http://vmreviews.qa-lab.sendmail.com/reviews/account/login/?next_page=/reviews/dashboard/ invalid syntax (parser.py, line 23) Traceback (most recent call last): File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ core/handlers/base.py, line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.4/site-packages/Djblets-0.6.7-py2.4.egg/ djblets/auth/views.py, line 80, in login return render_to_response(template_name, context) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ shortcuts/__init__.py, line 20, in render_to_response return HttpResponse(loader.render_to_string(*args, **kwargs), **httpresponse_kwargs) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/loader.py, line 183, in render_to_string return t.render(Context(dictionary)) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/base.py, line 123, in render return self._render(context) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/base.py, line 117, in _render return self.nodelist.render(context) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/base.py, line 744, in render bits.append(self.render_node(node, context)) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/base.py, line 757, in render_node return node.render(context) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/loader_tags.py, line 127, in render return compiled_parent._render(context) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/base.py, line 117, in _render return self.nodelist.render(context) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/base.py, line 744, in render bits.append(self.render_node(node, context)) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/base.py, line 757, in render_node return node.render(context) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/loader_tags.py, line 64, in render result = block.nodelist.render(context) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/base.py, line 744, in render bits.append(self.render_node(node, context)) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/base.py, line 757, in render_node return node.render(context) File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ template/defaulttags.py, line 313, in render ... File /usr/lib/python2.4/site-packages/Django-1.3-py2.4.egg/django/ core/urlresolvers.py, line 197, in _populate for pattern in reversed(self.url_patterns): File
