[Zope-Checkins] SVN: Zope/branches/2.12/src/HelpSys/APIHelpTopic.py Fix HelpSys to work with zope.interface.Interface as it did before the deprecated methods of scarecrow Interface.Interface were remo
Log message for revision 105060: Fix HelpSys to work with zope.interface.Interface as it did before the deprecated methods of scarecrow Interface.Interface were removed. Changed: U Zope/branches/2.12/src/HelpSys/APIHelpTopic.py -=- Modified: Zope/branches/2.12/src/HelpSys/APIHelpTopic.py === --- Zope/branches/2.12/src/HelpSys/APIHelpTopic.py 2009-10-14 08:35:10 UTC (rev 105059) +++ Zope/branches/2.12/src/HelpSys/APIHelpTopic.py 2009-10-14 08:54:25 UTC (rev 105060) @@ -48,8 +48,8 @@ if type(v)==types.ClassType: # A class. self.apis.append(APIDoc(v, 0)) -elif (hasattr(v, 'isImplementedByInstancesOf')): -# A scarecrow interface. +elif (hasattr(v, 'implementedBy')): +# A zope.interface.Interface. self.apis.append(APIDoc(v, 1)) elif type(v)==types.FunctionType: # A function ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/trunk/src/HelpSys/APIHelpTopic.py Merge 105060 from branch 2.12: Fix HelpSys to work with zope.interface.Interface as it did before the deprecated methods of scarecrow Interf
Log message for revision 105062: Merge 105060 from branch 2.12: Fix HelpSys to work with zope.interface.Interface as it did before the deprecated methods of scarecrow Interface.Interface were removed. Changed: U Zope/trunk/src/HelpSys/APIHelpTopic.py -=- Modified: Zope/trunk/src/HelpSys/APIHelpTopic.py === --- Zope/trunk/src/HelpSys/APIHelpTopic.py 2009-10-14 08:54:58 UTC (rev 105061) +++ Zope/trunk/src/HelpSys/APIHelpTopic.py 2009-10-14 08:57:25 UTC (rev 105062) @@ -48,8 +48,8 @@ if type(v)==types.ClassType: # A class. self.apis.append(APIDoc(v, 0)) -elif (hasattr(v, 'isImplementedByInstancesOf')): -# A scarecrow interface. +elif (hasattr(v, 'implementedBy')): +# A zope.interface.Interface. self.apis.append(APIDoc(v, 1)) elif type(v)==types.FunctionType: # A function ___ Zope-Checkins maillist - Zope-Checkins@zope.org https://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-dev] Zope Tests: 8 OK
Summary of messages to the zope-tests list. Period Tue Oct 13 12:00:00 2009 UTC to Wed Oct 14 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Oct 13 20:46:13 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012776.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Oct 13 20:48:13 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012777.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Tue Oct 13 20:50:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012778.html Subject: OK : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Oct 13 20:52:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012779.html Subject: OK : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Tue Oct 13 20:54:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012780.html Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Tue Oct 13 20:56:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012781.html Subject: OK : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Tue Oct 13 20:58:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012782.html Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Tue Oct 13 21:00:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-October/012783.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] zope.site.hooks
Hey, Fabio Tranchitella wrote: [snip] I tried to implement my idea here: svn://svn.zope.org/repos/main/zope.component/branches/conditional-zope.security This is a quite intrusive change, so please take it as a suggestion and not as a real proposal: is this the right approach? That's more or less what I have in mind. The suggestions are just about trying to make it prettier. This: if not SECURITY_SUPPORT: raise ConfigurationError(security proxied components are not supported because zope.security is not available) could simply become a function you can call: check_security_support() That'd be far less repetitive code. I'd also place everything you put in the 'else' branch for the import error check into a separate module. This way you don't have to define a lot of stuff on the top level. When you see something from this module in use, you *know* check_security_support() should have been executed successfully. Further improvements might be possible by an approach where instead of doing a lot of conditional checks everywhere, you define the things that do need security in such a way that they just proceed gracefully without security as well (or raise the appropriate errors). For instance, proxify() might simply not do anything, the same with protectedFactory. I did not (yet) write all the tests needed (and I don't like the idea of duplicating the tests in zcml_conditional.txt, to be honest). I think we need to try to separate security-related tests from the rest of the tests, and test that they fail with the right errors if zope.security is not present and do the right thing when it is. It would also be nice to be able to run the other tests with or without zope.security - the result should be identical. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope] Problem with Zodb connections pool
Hi all, I've a system with Zope 2.8.8 that since some weeks is very slow. The python process keeps busy the CPU (98-99%) and the memory used by the process is growing up. Every day a script makes a pack of the ZODB and restarts Zope so the Data.fs size is stable (about 350MB). In the event.log I can see many of this warnings: 2009-10-14T11:59:14 WARNING ZODB.DB DB.open() has 8 open connections with a pool_size of 7 What does it mean? I can see also some of these messages: 2009-10-14T12:14:16 INFO ZODB.Conflict database conflict error... According to you, are the two messages related? Thank you very much claudio ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Problem with Zodb connections pool
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Claudio Battaglino wrote: Hi all, I've a system with Zope 2.8.8 that since some weeks is very slow. The python process keeps busy the CPU (98-99%) and the memory used by the process is growing up. Every day a script makes a pack of the ZODB and restarts Zope so the Data.fs size is stable (about 350MB). In the event.log I can see many of this warnings: 2009-10-14T11:59:14 WARNING ZODB.DB DB.open() has 8 open connections with a pool_size of 7 What does it mean? Likely something in your application is leaking connections (and therefore RAM). Normally each worker thread gets a connection from the pool at the start of the request, uses it, and then returns it to the pool at the end of the request. If you are using the default configuration for number of threads (4), then something has leaked four connections (assuming your server is busy at the time you see that log message). You should examine the Debug Information page in the ZMI control panel to get information for diagnosing the leak. I can see also some of these messages: 2009-10-14T12:14:16 INFO ZODB.Conflict database conflict error... According to you, are the two messages related? No. Conflict errors occur normally, whenever simultaneous requests cause writes to the same objects. The request whose transaction commits later gets retried, up to three times; if it still conflicts, then the request returns an error, and you see the message in your logfile. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrVrT4ACgkQ+gerLs4ltQ5HagCeJ1X32zT+LOMasY90fzmBolzR Q6MAn3qHhkjENxxr7B24z54fsj4TCfQT =ETsW -END PGP SIGNATURE- ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Problem with Zodb connections pool
2009/10/14 Tres Seaver tsea...@palladion.com: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Claudio Battaglino wrote: Hi all, I've a system with Zope 2.8.8 that since some weeks is very slow. The python process keeps busy the CPU (98-99%) and the memory used by the process is growing up. Every day a script makes a pack of the ZODB and restarts Zope so the Data.fs size is stable (about 350MB). In the event.log I can see many of this warnings: 2009-10-14T11:59:14 WARNING ZODB.DB DB.open() has 8 open connections with a pool_size of 7 What does it mean? Likely something in your application is leaking connections (and therefore RAM). Normally each worker thread gets a connection from the pool at the start of the request, uses it, and then returns it to the pool at the end of the request. If you are using the default configuration for number of threads (4), then something has leaked four connections (assuming your server is busy at the time you see that log message). You should examine the Debug Information page in the ZMI control panel to get information for diagnosing the leak. Tres is right. Use the Debug Information. Especially look for requests (the last big table) that take longer than 1 second. The table will provide some information about what request is taking so long. Additionally/Alternatively you can check out DeadlockDebugger which you have to install manually for your Zope and you get the same information but instead of information about the requests you get tracebacks from within the code that is executing the requests. I can see also some of these messages: 2009-10-14T12:14:16 INFO ZODB.Conflict database conflict error... According to you, are the two messages related? No. Conflict errors occur normally, whenever simultaneous requests cause writes to the same objects. The request whose transaction commits later gets retried, up to three times; if it still conflicts, then the request returns an error, and you see the message in your logfile. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Design http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrVrT4ACgkQ+gerLs4ltQ5HagCeJ1X32zT+LOMasY90fzmBolzR Q6MAn3qHhkjENxxr7B24z54fsj4TCfQT =ETsW -END PGP SIGNATURE- ___ Zope maillist - z...@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev ) -- Peter Bengtsson, work www.fry-it.com home www.peterbe.com hobby www.issuetrackerproduct.com fun crosstips.org ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope-CMF] CMF 2.2 release?
Am 14.10.2009, 22:26 Uhr, schrieb Eric Steele ems...@psu.edu: I've managed to completely neglect this during our PLIP push, shame on me... Get on your knees! I'll be at the post-Plone conference sprints. Would anyone be willing to work with me to wrap up the remaining bits holding up a CMF release? I can try to drum up support from the Plone ranks. Plone 4.0 is 96% merged and we'll be hoping to cut an alpha very soon. Me and Jens will be there and Jens will be holding the Hat of Shame over my head. Not sure who will be there and who'll be sober. Better order the langos in advance! ;-) Charlie -- Charlie Clark Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-938-5360 GSM: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
