Re: RB 1.6.12 upgrade to 1.7.1 is failed. Web (WSGI) problem.
2012. december 28., péntek 12:10:00 UTC+1 időpontban Viktor Jozsa a következőt írta: Hi Christian, I upgreaded my RB to 1.7.1. I don't found error in process, but my web page is not good.I attached the apache2.log and web page picture.. [Fri Dec 28 10:53:13 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/template/defaulttags.py:1235: DeprecationWarning: The syntax for the url template tag is changing. Load the `url` tag from the `future` tag library to start using the new behavior. [Fri Dec 28 10:53:13 2012] [error] category=DeprecationWarning) [Fri Dec 28 11:53:14 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/simple.py:8: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Fri Dec 28 11:53:14 2012] [error] DeprecationWarning [Fri Dec 28 10:53:19 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Fri Dec 28 10:53:19 2012] [error] DeprecationWarning [Fri Dec 28 10:53:19 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Fri Dec 28 10:53:19 2012] [error] DeprecationWarning [Fri Dec 28 10:53:19 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Fri Dec 28 10:53:19 2012] [error] DeprecationWarning [Fri Dec 28 10:53:19 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Fri Dec 28 10:53:19 2012] [error] DeprecationWarning [Fri Dec 28 10:53:19 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Fri Dec 28 10:53:19 2012] [error] DeprecationWarning [Fri Dec 28 10:53:19 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Fri Dec 28 10:53:19 2012] [error] DeprecationWarning [Fri Dec 28 11:53:20 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead. [Fri Dec 28 11:53:20 2012] [error] use STATIC_URL instead., DeprecationWarning) [Fri Dec 28 11:53:20 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead. [Fri Dec 28 11:53:20 2012] [error] use STATIC_URL instead., DeprecationWarning) [Fri Dec 28 11:53:20 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead. [Fri Dec 28 11:53:20 2012] [error] use STATIC_URL instead., DeprecationWarning) [Fri Dec 28 11:53:20 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead. [Fri Dec 28 11:53:20 2012] [error] use STATIC_URL instead., DeprecationWarning) [Fri Dec 28 11:53:20 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead. [Fri Dec 28 11:53:20 2012] [error] use STATIC_URL instead., DeprecationWarning) [Fri Dec 28 11:53:20 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/template/defaulttags.py:1235: DeprecationWarning: The syntax for the url template tag is changing. Load the `url` tag from the `future` tag library to start using the new behavior. [Fri Dec 28 11:53:20 2012] [error] category=DeprecationWarning) [Fri Dec 28 11:53:20 2012] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/template/defaulttags.py:1235: DeprecationWarning: The syntax for the url template tag is changing. Load the `url` tag from the `future` tag library to start using the new behavior. [Fri Dec 28 11:53:20 2012] [error]
Re: RB 1.6.12 upgrade to 1.7.1 is failed. Web (WSGI) problem.
Hi Christian! Of course! I attached the apache2.conf: LockFile ${APACHE_LOCK_DIR}/accept.lock PidFile ${APACHE_PID_FILE} Timeout 500 KeepAlive On MaxKeepAliveRequests 100 KeepAliveTimeout 30 IfModule mpm_prefork_module StartServers 5 MinSpareServers 5 MaxSpareServers 10 MaxClients 150 MaxRequestsPerChild 0 /IfModule IfModule mpm_worker_module StartServers 2 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxClients 150 MaxRequestsPerChild 0 /IfModule IfModule mpm_event_module StartServers 2 MaxClients 150 MinSpareThreads 25 MaxSpareThreads 75 ThreadLimit 64 ThreadsPerChild 25 MaxRequestsPerChild 0 /IfModule User ${APACHE_RUN_USER} Group ${APACHE_RUN_GROUP} AccessFileName .htaccess Files ~ ^\.ht This is default configuration file. Regards, Viktor -- 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 can't find git
I'm trying to run post-review from windows 7 from a git base directory. It doesn't seem to be finding git, and the -d option isn't indicating how it might be looking. Output is below. A different post suggested it was running 'git rev-parse --git-dir'. There is a git executable (a symbolic link, actually) on the path, and I can run that successfully from the command line. Any idea what I might try? DEBUG:root:Checking for a CVS repository... DEBUG:root:Checking for a ClearCase repository... DEBUG:root:Checking for a Git repository... DEBUG:root:Checking for a Mercurial repository... DEBUG:root:Checking for a Perforce repository... DEBUG:root:Checking for a Plastic repository... DEBUG:root:Checking for a Subversion repository... RBTools 0.4.2 Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] Running on Windows-7-6.1.7601-SP1 Home = C:\Users\jglazer\AppData\Roaming Current Directory = C:\Users\jglazer\code\testproject Checking the repository type. Errors shown below are mostly harmless. The current directory does not contain a checkout from a supported source code repository. -- 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: Email setup help
Filed an enhancement at http://code.google.com/p/reviewboard/issues/detail?id=2840 and posted a patch at http://reviews.reviewboard.org/r/3707/ - Raja On Friday, December 28, 2012 2:42:53 AM UTC+5:30, Christian Hammond wrote: In theory, it could, but it would probably need a little bit of new code to provide a signal we can emit on close/reopen. I wouldn't be opposed to having this feature as part of Review Board, so long as it's optional. It's pretty minimal. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Dec 27, 2012 at 6:31 AM, Michael Zhilin miz...@gmail.comjavascript: wrote: Hi Christian, Could it be implemented as extension or not? Thank you, Michael Zhilin On Dec 26, 2012, at 23:57, Christian Hammond chi...@chipx86.comjavascript: wrote: Hi Peer, We don't e-mail when closing review requests. We only e-mail for new updates and reviews/replies. I'd be happy to take a patch that provides it and makes it optional (off by default in order to not increase e-mail load). Christian On Dec 26, 2012, at 5:08 AM, Peer peerm...@gmail.com javascript: wrote: Hi Christian, mail notify for close submitted, action is not working. is this notification not active by default. if its by default. please let me know if i can enable a mail notify for submitted action . Thanks, Peer On Thursday, July 12, 2012 2:26:56 AM UTC+5:30, Christian Hammond wrote: Right, it's only on publish, reviews, and replies. We're told we're too noisy as it is, so doing it on drafts would probably not be in our best interest ;) Also, it's just not information most users would care about. Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Jul 11, 2012 at 1:45 PM, superakuma hwo...@gmail.com wrote: Christian, Email works now. We use zimbra for mail and it allows relays. Have also configured exim locally and did a telnet localhost 25 to test it. It works so I set this: Mail Server: localhost port: 25 No username and password After I publish a review, I do see an email. I was hoping that I get email notifications after I create a draft review via post-review but it seems like emails are only sent when you make a publish action. Thanks, Howard On Wednesday, July 11, 2012 11:28:57 AM UTC-7, Christian Hammond wrote: We show when there's an error, but not when a mail was sent. Can you describe your setup more? What SMTP server are you using, and is it on the same machine? What action are you performing where you expect e-mails to be sent? Are the recipients on mailing lists, or individuals? Gmail/Yahoo/etc, or company e-mail? Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Jul 11, 2012 at 9:45 AM, superakuma hwo...@gmail.com wrote: Thanks for the quick response. I don't see anything going to our mail server and nothing in the RB log. Is there a way to see something in the log that shows it tried to send the emails? Some debugging message would help. Thanks, Howard On Tuesday, July 10, 2012 10:46:49 PM UTC-7, Christian Hammond wrote: Hi Howard, I'm not aware of any bug. Plenty of people are using 1.6.9 with mail servers, including us. Did you check the Review Board log or the mail server log? Might be worth seeing what the mail server says. Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Tue, Jul 10, 2012 at 10:29 PM, superakuma hwo...@gmail.comwrote: I have RB 1.6.9 installed and got everything working but the email setup. I input a valid SMTP server and even tried it out using telnet test. That works. I checked the log and nothing shows up. Is there anyway for me to debug this to see what's wrong or there is a bug in this release? Thanks, Howard -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**donate/http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**users/http://www.reviewboard.org/users/ -~--~~~~--**~~--~--~--- To unsubscribe from this group, send email to reviewboard...@** googlegroups.com For more options, visit this group at http://groups.google.com/** group/reviewboard?hl=enhttp://groups.google.com/group/reviewboard?hl=en -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**don**ate/http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**use**rs/http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to
Re: Issue 2664 in reviewboard: Upgrade to Review Board 1.6.9 but can't set up a GitHub repo
Comment #7 on issue 2664 by rajas...@gmail.com: Upgrade to Review Board 1.6.9 but can't set up a GitHub repo http://code.google.com/p/reviewboard/issues/detail?id=2664 You might want to setup the env variable for https_proxy instead of http_proxy since you are accessing a https url. From http://docs.python.org/2/library/urllib2.html#urllib2.ProxyHandler, it seems that the default is to read the environment variable protocol_proxy and since your github url is https, that could be the problem -- 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 2826 in reviewboard: File-based caches don't install properly on 1.7RC1
Comment #3 on issue 2826 by rajas...@gmail.com: File-based caches don't install properly on 1.7RC1 http://code.google.com/p/reviewboard/issues/detail?id=2826 Django seems to have changed the format of directory accepted in the FileBasedCache between versions 1.2 and 1.3. Ive posted a patch at http://reviews.reviewboard.org/r/3706/ -- 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 2662 in reviewboard: Repository List Resource web service API doesn't return all repos
Comment #2 on issue 2662 by rajas...@gmail.com: Repository List Resource web service API doesn't return all repos http://code.google.com/p/reviewboard/issues/detail?id=2662 This seems to be a limit set in djblets/webapi/core.py:WebAPIResponsePaginated. Although the links array should point to the next page in case the total results is greater than what is requested, I agree with OP that if its requested, it should return all the records. Can this line: max_results = \ min(int(request.GET.get('max-results', default_max_results)), max_results_cap) be changed to try: max_results = int(request.GET.get('max-results')) except ValueError: max_results = default_max_results We could remove the max_results_cap variable as well with the above change. From a performance standpoint, it could be an issue if we have lots of results obtained through the API. Since the original design does provide a next url for pagination, that seems a decent solution as long as its documented. -- 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 2826 in reviewboard: File-based caches don't install properly on 1.7RC1
Updates: Status: Fixed Comment #4 on issue 2826 by trowb...@gmail.com: File-based caches don't install properly on 1.7RC1 http://code.google.com/p/reviewboard/issues/detail?id=2826 Fixed in release-1.7.x (624517c). Thanks! -- 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 2840 in reviewboard: Send Email when review request is closed
Status: New Owner: Labels: Type-Enhancement Priority-Medium New issue 2840 by rajas...@gmail.com: Send Email when review request is closed http://code.google.com/p/reviewboard/issues/detail?id=2840 *NOTE: If you have a patch, please submit it to http://reviews.reviewboard.org/ What version are you running? 1.7.1 What's the URL of the page this enhancement relates to, if any? Local instance Describe the enhancement and the motivation for it. This was requested in https://groups.google.com/forum/#!msg/reviewboard/ROn8rb1qJg0/3G904h402CIJ When a review request is closed, it would be good to email at that time. Make this optional so that email flooding is avoided. What operating system are you using? What browser? Ubuntu Precise/Chrome Please provide any additional information below. Patch available at http://reviews.reviewboard.org/r/3707/ -- 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 581 in reviewboard: Users should be able to specify their default Dashboard view
Comment #12 on issue 581 by rajas...@gmail.com: Users should be able to specify their default Dashboard view http://code.google.com/p/reviewboard/issues/detail?id=581 Posted a patch for this at http://reviews.reviewboard.org/r/3653/ -- 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 2740 in reviewboard: Trophies for prime numbers
Comment #2 on issue 2740 by rajas...@gmail.com: Trophies for prime numbers http://code.google.com/p/reviewboard/issues/detail?id=2740 Posted a patch for this at http://reviews.reviewboard.org/r/3639/ -- 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.