- Zope-Dev - Zope lists

Please vote about conflict errors logging
by Florent Guillaume 09 Dec '05

09 Dec '05

Please vote for the level at which you want to log retried conflict errors. These are the ConflictErrors that aren't returned to the user but automatically retried by the Zope publisher. 1. Do you want these ConflictErrors retried logs to be at level: - INFO - BLATHER - DEBUG - not logged - other 2. In addition, please specify if you feel those retried ConflictErrors should have their full traceback logged? - Yes, with traceback - No, without traceback 3. Finally, please tell us if the ConflictErrors that *can't* be retried (and are returned to the user as an error, and are also logged to the error_log) should be additionally explicitely logged to the event log, and at which level: - ERROR - not logged - other (Also, if you feel the logging should be different between 2.8 and 2.9, please say so.) I'll wait until Wednesday morning to collect results. Thanks, Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

14 32

Re: [Zope-Checkins] SVN: Zope/branches/ajung-zpt-integration/lib/python/Products/ZPT/ZPT.py eeek...Zope 3 ZPTs now work in Zope 2 :-)
by Sidnei da Silva 09 Dec '05

09 Dec '05

On Fri, Dec 09, 2005 at 09:25:51AM -0500, Andreas Jung wrote: | +try: | + from webdav.Lockable import ResourceLockedError | + from webdav.WriteLockInterface import WriteLockInterface | + SUPPORTS_WEBDAV_LOCKS = 1 | +except ImportError: | + SUPPORTS_WEBDAV_LOCKS = 0 Never understood this. The interface has been there since when? Zope 2.6? Why is it in a try: except in new code? -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com

1 0

Zope tests: 8 OK
by Zope tests summarizer 09 Dec '05

09 Dec '05

Summary of messages to the zope-tests list. Period Thu Dec 8 12:01:02 2005 UTC to Fri Dec 9 12:01:02 2005 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Thu Dec 8 23:19:42 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003746.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Dec 8 23:21:12 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003747.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Dec 8 23:22:42 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003748.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Dec 8 23:24:12 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003749.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Thu Dec 8 23:25:42 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003750.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Dec 8 23:27:12 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003751.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Dec 8 23:28:43 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003752.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Thu Dec 8 23:30:13 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003753.html

1 0

Zope tests: 8 OK
by Zope tests summarizer 08 Dec '05

08 Dec '05

Summary of messages to the zope-tests list. Period Wed Dec 7 12:01:01 2005 UTC to Thu Dec 8 12:01:01 2005 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Wed Dec 7 22:13:24 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003738.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Dec 7 22:14:54 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003739.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Dec 7 22:16:24 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003740.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Dec 7 22:17:54 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003741.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Wed Dec 7 22:19:24 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003742.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Dec 7 22:20:54 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003743.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Dec 7 22:22:24 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003744.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Wed Dec 7 22:23:54 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003745.html

1 0

Tracking long-running requests
by Chris Withers 08 Dec '05

08 Dec '05

Hi Dieter, > You err: I do want to see them in the logfile and > I stole Florents idea to use "threadframe" (in his "DeadlockDebugger") > to include a traceback for long running requests in the logfile. > This way, it is > easy not only to identify long running requests but also to > get hints where they are spending their time... > > > You will not believe how fast this has eliminated our remaining > long running requests and especially to track down > a non deterministic rarely occuring apparent deadlock situation... Is this code available anywhere? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

3 4

zLOG deprecation?
by Chris Withers 08 Dec '05

08 Dec '05

Hi All, Is zLOG deprecated? If not, it should be... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

5 12

New testrunner on the Zope 2 trunk.
by Jim Fulton 07 Dec '05

07 Dec '05

I just checked in a new test runner on the trunk. It is mostly backward compatible with the old test runner. You can get help on the test runner by running it with -h. There is more extensive documentation in lib/python/zope/testing/testrunner.txt. Note that the new test runner complains if test_suite functions don't return test suites. There is a zope.i18n test suite that it currently complains about. Unfortunately, I can't just fix this because it is an svn:external and it will be too painful to create a tag with the necessary fix in the short term. I expect we will be integrating a newer version of Zope 3 later in the week and we'll take care of this then. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

3 11

Zope tests: 8 OK
by Zope tests summarizer 07 Dec '05

07 Dec '05

Summary of messages to the zope-tests list. Period Tue Dec 6 12:01:02 2005 UTC to Wed Dec 7 12:01:02 2005 UTC. There were 8 messages: 8 from Zope Unit Tests. Tests passed OK --------------- Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:15:45 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003730.html Subject: OK : Zope-2_6-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:17:15 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003731.html Subject: OK : Zope-2_7-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:18:45 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003732.html Subject: OK : Zope-2_7-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:20:15 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003733.html Subject: OK : Zope-2_8-branch Python-2.3.5 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:21:45 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003734.html Subject: OK : Zope-2_8-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:23:15 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003735.html Subject: OK : Zope-2_9-branch Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:24:45 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003736.html Subject: OK : Zope-trunk Python-2.4.2 : Linux From: Zope Unit Tests Date: Tue Dec 6 22:26:15 EST 2005 URL: http://mail.zope.org/pipermail/zope-tests/2005-December/003737.html

1 0

version.txt [was: make sdist]
by Philipp von Weitershausen 06 Dec '05

06 Dec '05

Andreas Jung wrote: > make sdist: > > ajung@sentinel:~/sandboxes/Zope-2.9/2.9.0b1: make sdist > zpkg -C /develop/sandboxes/Zope-2.9/2.9.0b1/releases/Zope2.cfg > 'version.txt' doesn't match any files in <collection> > (in /develop/sandboxes/Zope-2.9/2.9.0b1/lib/python/zope/app/PACKAGE.cfg) > ---- > temporary files are in /tmp/zpkg-50vtPj > make: *** [sdist] Error 1 This is a very recent problem and a result of Jim's inconsistent handling of the "version.txt" matter yesterday. http://dev.zope.org/Zope3/MakingARelease says that zope.app/version.txt should be created on a tag and zope.app/PACKAGE.cfg should also be modified to include version.txt *on the tag*. Jim did the latter on the Zope 3.2 branch. The Zope 2.9 externals currently point to the Zope 3.2 branch which references version.txt in PACKAGE.cfg but doesn't have one. Only the 3.2.0beta1 tag has it. I think that a) zope.app/PACKAGE.cfg should not mention version.txt when there isn't one, meaning on the branch b) Zope 2.9 externals should now point to the Zope 3.2.0beta1 tag. By the way, this issue reminds me: We haven't figured out how to handle Zope 2's version.txt at all! I totally forgot about it. Zope 2 expects a version.txt in Zope/lib/python, but zpkg has no way to support a data file that isn't in a Python package. So there would be no way to package it nor to install it (I don't think distutils knows how to install a non-package-related datafile either). I propose that the future place for Zope 2's version.txt is the Zope2 package. Some code inside Zope 2 that reads version info from version.txt would have to be changed for that, though. This should be fixed for the 2.9 beta, meaning today. I'm outside svn+ssh access range right now, so either you do it, Andreas, or you wait until I'm at home in about 5 hours. Philipp ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 5

Re: SVN: Zope/branches/2.9/ deprecated FastCGI
by Philipp von Weitershausen 06 Dec '05

06 Dec '05

Andreas Jung wrote: > Log message for revision 40469: > deprecated FastCGI > > > Changed: > U Zope/branches/2.9/doc/CHANGES.txt > U Zope/branches/2.9/doc/WEBSERVER.txt > U Zope/branches/2.9/lib/python/ZServer/datatypes.py > [snip] > Modified: Zope/branches/2.9/lib/python/ZServer/datatypes.py > =================================================================== > --- Zope/branches/2.9/lib/python/ZServer/datatypes.py 2005-12-02 13:45:58 UTC (rev 40468) > +++ Zope/branches/2.9/lib/python/ZServer/datatypes.py 2005-12-02 13:49:55 UTC (rev 40469) > @@ -132,6 +132,11 @@ > > class FCGIServerFactory(ServerFactory): > def __init__(self, section): > + > + import warnings > + warnings.warn("Using FastCGI is deprecated. You should use mod_proxy " > + "to run Zope with Apache", DeprecationWarning) > + > import socket > if section.address.family == socket.AF_INET: > address = section.address.address Andreas, this checkin made the tests fail for the build-bot (http://mail.zope.org/pipermail/zope-tests/2005-December/003728.html) Since you didn't use stacklevel=2 in the warnings.warn() call, it's hard to see where FCGIServerFactory() is called from. Maybe tests? Philipp

1 2