Re: post-review from windows fails
On 15.03.2011, at 21:46, Christian Hammond wrote:
Are you behind a proxy server?
No, I am not behind a proxy server.
With 0.3.2, can you run with --debug and provide the output?
The output is attached as debug_output_rbtools_0.3.2.txt
I can report some details concerning the problem:
1. While playing around with the login problems I found out, that
allowing anonymous read access brings post-review some steps further,
but then again it stops asking for Web-API credentials although user
name and password were provided via command line. See
debug_output_anonymous_read.txt for the output.
2. The behavior of post-review 0.2 on osx does not differ from the one
on windows, that was wrong. The difference resulted from the fact,
that I had a valid cookie in my .postreview-cookies.txt on osx. As
soon as I copy that cookie to the windows machine, I can authenticate
there as well.
3. With the valid cookie in my .postreview-cookies.txt file it seems
to to ignore any credentials on the command line. I start pushing a
diff-file with a --username= argument, but without password. post-
review then prompts for a password, as expected. But no matter what I
type there, the operation will always succeed due to the cookie. Does
review-board use the cookie as fallback authentication method if the
password is false? I would expect the operation to fail if I provide a
specific user name and an invalid password is typed. Maybe this is
related to this older bug:
http://code.google.com/p/reviewboard/issues/detail?id=762
See debug_output_withoutcookie.txt for an example.
4. My normal authentication mechanism is ActiveDirectory. Changing back to
standard authentication does not solve the problem.
Sorry for re-posting the message, I think I tamed the mail-client now.
Regards, Ruben
--
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=enC:\Promptpost-review --submit-as=username --target-groups= --target-
people=targetuser --diff-filename=rbDiff_File --repository-url=https://
subversion.lan/dev --bugs-closed= --
summary=file.ending/.otherending@revision --description=asdf --
server=http://reviewboard.lan --username=admin --publish --debug
RBTools 0.3.2
Home = C:\Users\rstein.MR\AppData\Roaming
svn info https://subversion.lan/dev
diff --version
repository info: Path: https://subversion.lan/dev, Base path: /, Suppor
ts changesets: False
HTTP GETting api/
== HTTP Authentication Required
Enter authorization information for Web API at reviewboard.fme.lan
Password:
HTTP GETting http://reviewboard.lan/api/info/
Using the new web API
HTTP GETting http://reviewboard.lan/api/repositories/
HTTP GETting http://reviewboard.lan/api/repositories/1/
HTTP GETting http://reviewboard.lan/api/repositories/1/info/
HTTP GETting http://reviewboard.lan/api/repositories/2/
HTTP GETting http://reviewboard.lan/api/repositories/2/info/
repository info: Path: https://subversion.lan/dev, Base path: /, Suppor
ts changesets: False
Attempting to create review request on https://subversion.lan/dev for N
one
Submitting the review request as rstein
HTTP POSTing to http://reviewboard.lan/api/review-requests/: {'submit_as
': 'rstein', 'repository': u'https://subversion.lan/dev'}
Review request created
Attempting to set field 'target_people' to 'targetuser' for review request
'127'
HTTP PUTting to http://reviewboard.lan/api/review-requests/127/draft/: {
'target_people': 'admin,rstein'}
Attempting to set field 'summary' to 'file.ending/.otherending@revision' f
or review request '127'
HTTP PUTting to http://reviewboard.lan/api/review-requests/127/draft/: {
'summary': 'file.ending/.otherending@revision'}
Attempting to set field 'description' to 'asdf' for review request '127'
HTTP PUTting to http://reviewboard.fme.lan/api/review-requests/127/draft/: {
'description': 'asdf'}
Uploading diff, size: 2838
HTTP POSTing to http://reviewboard.lan/api/review-requests/127/diffs/: {
'basedir': '/'}
Publishing
HTTP PUTting to http://reviewboard.lan/api/review-requests/127/draft/: {
'public': 1}
Review request #127 posted.
http://reviewboard.lan/r/127/ C:\Promptpost-review --submit-as=username --target-groups= --target-
people=targetuser --diff-filename=rbDiff_File --repository-url=https://
subversion.lan/dev --bugs-closed= --
summary=file.ending/.otherending@revision --description=asdf --
server=http://reviewboard.lan --username=dummyUser --
password=DummyPasswd --publish --debug
RBTools 0.3.2
Home = C:\Prompt
svn info https://suversion.landev
diff --version
repository info: Path: https://suversion.lan/dev, Base path: /, Suppor
ts changesets: False
HTTP GETting api/
HTTP GETting
Re: Setting target-groups or target-people with post-review fails
Hello again, I now realized, that only the user set with --submit-as can see the real content of the review-request draft. I was able to see only those submitted as admin correctly, because I was logged in as admin. But what is the reason for this? Are the fields stored user-local until the review is published? I think it is strange to show the admin a publish review button that publishes a completely different review-request than the user intended to post. At least admins should see the submitted fields, should they not? Regards, Ruben -- 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: ReviewBoard hanging when uploading a diff
Clear Case is kind of a semi-supported SCM from our point of view, because we don't have a license and can't really test anything on it. However, it's had a number of contributions from other people. I'm looping Jan into this conversation, who may be able to help more. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Mar 23, 2011 at 1:57 PM, akochnev akoch...@gmail.com wrote: I tried a few more permutations of the repository setup, all to no avail. 1. Snapshot view on the RB server Hosting Service : Custom repository Type : Clear Case Path : D:\snapshots\RC2009_int_reviewboard_ss This is the path to the snapshot view 2. Dynamic view mounted at the root of a drive ( Hosting Service : Custom repository Type : Clear Case Path : Y:\ The docs seemed to suggest that the path would just be the drive One thing to note is that trying to upload a diff doesn't impair the rest of the application - while the upload spinner is spinning, I can open up a new tab and interact with the application. The most difficult part is that there is no output produced anywhere when this happens (e.g. even if I enable DEBUG=true in conf/settings_local.py). Can anyone who has used RB w/ ClearCase provide any tips on a working setup ? On Mar 23, 4:06 pm, akochnev akoch...@gmail.com wrote: This seems to work as expected with a Mercurial repository. Thus, it would appear that the issue here might be coming from the ClearCase support on Windows. Following a note that only dynamic views are supported with ClearCase, I've set up a dynamic view on my M: drive (M: \RC2009_int_reviewboard) . Then in the ClearCase repository information, I've filled in the follwoing : Hosting Service : Custom repository Type : Clear Case Path : M:\RC2009_int_reviewboard This is the set up that makes uploading diffs hang. Any tips on how to deal with this (or just to debug to see where the issue is) would be greatly appreciated. On Mar 23, 1:20 pm, akochnev akoch...@gmail.com wrote: I've followed the instructions to install reviewboard 1.5.4 with python 2.6, apache 2.2, mod_python , sqlite, memcached, patch, and mercurial 1.8.1 support on windows. The box itself has ClearCase installed so I'm trying to test out the Clear Case support as well (I've set up a CC repository in RB). When I try to create a new review request using post-review, the review request is created; however, when post-review tries to upload the diff file ReviewBoard hangs and the process never completes. When I try to create a new review request by uploading a diff through the web app, review board hangs and the request never completes (the spinner just keeps spinning) I tested uploading an image and that works fine - a directory structure gets created under media/uploaded/images, which seems to point out that the permissions on the upload directories are OK. I've looked both in the apache logs and in the logs folder in the rb site that I've created but i don't see any error messages. I've enabled Debug=True in conf/settings_local.py, but that didn't help either. I've tried running apache both as a system user and myself (the user used in the install process) to make sure that it's not some other permissions issue, but no luck there either. It feels like I'm missing something fundamental here - does anyone have any tips of where I could look to figure out why this is not working for me ? -- 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 -- 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: Review Board accepted to Google Summer of Code 2011 - Looking for mentors/ideas
I quite agree. A lot of that needs to be finished up. For some of it, we've had students go and finish up the project (or at least get further on it) and we'll probably continue to do that. There's always, of course, the need to deliver an interesting project that a student can work on. Finishing up someone else's work is not nearly as attractive as doing something new and exciting, so we need to do a bit of both, I think. Any specific branches you're wanting work done on? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Mar 23, 2011 at 10:42 PM, Jan Koprowski jan.koprow...@gmail.comwrote: Hi, Personally I will be glad if GSoC won't provide new features because there is too much cool stuff waiting on non-public branches I can't wait. IMHO this stuff wait too long and providing it to stable version should be the first goal. Regards, Jan On Thu, Mar 24, 2011 at 1:39 AM, Paul Schulz p...@mawsonlakes.org wrote: Hi Christian, On Tue, Mar 22, 2011 at 6:49 AM, Christian Hammond chip...@chipx86.com wrote: Hey everyone, We've been accepted again this year in Google's Summer of Code, a yearly event where students from around the world participate in open source projects, developing work experience and getting paid for it. (snip) We're also looking for ideas for projects, so if you have an idea for something awesome you'd like to see, just reply :) Thanks! Christian I work as a System Administrator for a large(ish) software engineering organisation and we are making use of and relying on ReviewBoard extensively in our software development process. Thank you for your efforts so far. Working with the Engineers, I more often hear about where the tool falls short, rather then about all the other really good things about ReviewBoard that actually works really well. The this end, I did an internal survey and came up with the following suggestions for feature improvements (see below). Thanks again for everyones efforts, Paul -- [Workflow] * Ship-it lockout or reset If the ship-it option has been selected, then no other changes/diffs can be uploaded. Comments can still be made, or if a change to the code is made, then the ship-it tags are removed. * Master Ship-it A reviewer (or group) with master ship-it power is all that is required to designate that a patch be shipped. * Automated Ship-it patch submission If a patch is marked as ship-it, than commit it to the repository. (All of the required information is available, including commit comment.) * Explicitly separate Reviewers from Shippers A shipper is someone with shipping powers, a reviewer is someone who is included in the review for comment. [Integration] * Bugzilla Add a bug report comment to a bug once a review has been completed. * Subversion Block a check in of a patch/changeset until a review has been approved (for some definition of approved). [Improvements] * Allow use of Full Name where usernames are displayed Reviewboard has access to full names, it should make more use of them. -- 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 -- Jan Koprowski -- 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 -- 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: Users are automatically created if authenticated through ldap
Christian, Is this a Reviewboard feature or a Django one? I would have guessed this was a Django behavior. I'm not even a Django (auth) novice, let alone expert, so sorry if this is a dumb question! Chris Christian Hammond wrote: Hi Pablo, No, there's no way to do this out of the box. You would need to write a custom auth backend that augments the LDAP backend to so this. There are plans in 1.6 to e-mail admins for new users. It'd make sense to have an option to disable new users until the admin approves them. If you want to file a bug on this, it'll help us track this. Christian On Wednesday, March 23, 2011, Pablo G pablo...@gmail.com wrote: Hi guys. I have a RB installation validating against an LDAP server. It looks like RB creates users in the local database whenever a user is correctly authenticated with LDAP. What I need is a way to disable this automatic user creation, so the site admin can decide which users in the full LDAP repository can access the RB. Is this possible? I am on RB 1.5.2. thanks a lot. -- 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 -- 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: Users are automatically created if authenticated through ldap
Which part? LDAP, or auth backends? Django provides basic support for auth backends. We provide extended support, and the LDAP, NIS, AD, etc. auth backends. Django also provides the basic stuff like database storage for users, active/inactive flags, etc. But it's up to us to make use of it all for the most part. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Mar 24, 2011 at 3:39 PM, Chris Clark chris.cl...@ingres.com wrote: Christian, Is this a Reviewboard feature or a Django one? I would have guessed this was a Django behavior. I'm not even a Django (auth) novice, let alone expert, so sorry if this is a dumb question! Chris Christian Hammond wrote: Hi Pablo, No, there's no way to do this out of the box. You would need to write a custom auth backend that augments the LDAP backend to so this. There are plans in 1.6 to e-mail admins for new users. It'd make sense to have an option to disable new users until the admin approves them. If you want to file a bug on this, it'll help us track this. Christian On Wednesday, March 23, 2011, Pablo G pablo...@gmail.com wrote: Hi guys. I have a RB installation validating against an LDAP server. It looks like RB creates users in the local database whenever a user is correctly authenticated with LDAP. What I need is a way to disable this automatic user creation, so the site admin can decide which users in the full LDAP repository can access the RB. Is this possible? I am on RB 1.5.2. thanks a lot. -- 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 -- 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 -- 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
Re: 500 - Internal Server Error | Review Board
Hi, Looks like a new python-dateutil was just released today that only works with Python 3, and it's being fetched. That's not good. We'll have to get out an update to be more specific about the version needed. Try getting rid of the old version (rm -rf /usr/lib/python2.4/site-packages/python_dateutil-2.0-py2.4.egg/) Then: easy_install -U python_dateutil==1.5 Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Mar 24, 2011 at 5:24 PM, storms v...@sendmail.com wrote: 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 =
RE: 500 - Internal Server Error | Review Board
Thanks... That fix the problem now I am able to see the login and registration GUI etc... Vincent From: chip...@gmail.com [mailto:chip...@gmail.com] On Behalf Of Christian Hammond Sent: Thursday, March 24, 2011 5:28 PM To: reviewboard@googlegroups.com Cc: Vincent Yee Subject: Re: 500 - Internal Server Error | Review Board Hi, Looks like a new python-dateutil was just released today that only works with Python 3, and it's being fetched. That's not good. We'll have to get out an update to be more specific about the version needed. Try getting rid of the old version (rm -rf /usr/lib/python2.4/site-packages/python_dateutil-2.0-py2.4.egg/) Then: easy_install -U python_dateutil==1.5 Christian -- Christian Hammond - chip...@chipx86.commailto:chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Mar 24, 2011 at 5:24 PM, storms v...@sendmail.commailto:v...@sendmail.com wrote: 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
Issue 2049 in reviewboard: Filtering requests at least by fields Repository, Reviews, Submitter
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2049 by gotische...@yahoo.de: Filtering requests at least by fields Repository, Reviews, Submitter http://code.google.com/p/reviewboard/issues/detail?id=2049 *NOTE: If you have a patch, please submit it to http://reviews.reviewboard.org/ What version are you running? 1.5.1 What's the URL of the page this enhancement relates to, if any? pages All review requests / My Dashboard Describe the enhancement and the motivation for it. I'm subscribed to make review for 3 projects (and this number will be increased with time). It is very difficult for me to find something related to project or review... E.g. I want to see: 1) requests for certain project (filtering by Repository would help; sorting by this column would not help, because having 3 projects all the time 1 is in the middle ;) 2) requests which are already reviewed (filtering by Reviews0 would help). If I filter by project then I could sort by this field; Now seems that I can't sort by reviews. 3) requests reviewed by me / not reviewed by me. I want to know which requests are already reviewed by me to check progress, as well as which requests are not reviewed by me (and maybe reviewed by somebody else, so I could check them to) 4) sometimes I got busy, so I can't review all requests; but I know that some people are good at coding, design etc. Few guys should be checked most of time. When I get busy I would save my time checking only these requests in first queue; so filtering by this column would help a lot (again, just sorting does not help that much..) What operating system are you using? What browser? Please provide any additional information below. Well, I am requesting for good, advanced filter for review requests -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2050 in reviewboard: Filtering files to review
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2050 by gotische...@yahoo.de: Filtering files to review http://code.google.com/p/reviewboard/issues/detail?id=2050 *NOTE: If you have a patch, please submit it to http://reviews.reviewboard.org/ What version are you running? 1.5.1 What's the URL of the page this enhancement relates to, if any? All review requests, My Dashboard, View Diff; sort of My/Users Settings Describe the enhancement and the motivation for it. I looked for similar requests/issues here, but didn't find... As reviewer, I don't want to see binary files, properties, xml files etc. while reviewing. Our review requests are created automatically by post-commit hook. As one possibility to make what I want is to create a wrapper for that hook command line which creates request to filter files I am not interested in. The problem is that somebody can be interested in reviewing xml or property files as well. I would be glad to have: 1) a setting that I want to review java, js files only. After setting it I would not see requests with other files (if they do not have java or js files); 2) when I review request I would not see changes of other files. 3) to improve usability it can be sort of checkbox to filter files or not so anybody could easy switch between modes. E.g. I see some code and I need to check related xml file commited (if any), then I don't need to change my settings by just exit filtered mode. What operating system are you using? What browser? Please provide any additional information below. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 1792 in reviewboard: post-review fails to upload diff with only binary files modified
Comment #2 on issue 1792 by jira.s...@gmail.com: post-review fails to upload diff with only binary files modified http://code.google.com/p/reviewboard/issues/detail?id=1792 It appears as though the problem is caused by svn. From what I've read, svn does not support binary diffs (they only support text). There is a way to get around this though: If you try to do an svn diff binary.bin you will probably get a Cannot display error. First set an editor so you can edit the file's svn properties. export EDITOR=yourPreferredEditor You can take a look at the properties file with: svn propedit svn:mime-type binary.bin And delete the svn:mime-type property with: svn propdel svn:mime-type binary.bin Then you should be able to get a diff using svn diff binary.bin (svn now thinks it is a text file). -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
