- Zope-Dev - Zope lists

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 26 May '08

26 May '08

Summary of messages to the zope-tests list. Period Sun May 25 11:00:00 2008 UTC to Mon May 26 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sun May 25 21:09:28 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009609.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sun May 25 21:03:26 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009605.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sun May 25 21:04:56 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009606.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sun May 25 21:06:27 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009607.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sun May 25 21:07:57 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009608.html

1 0

newInteraction problem
by Mattia Belletti 26 May '08

26 May '08

Hi all, I have quite a technical problem, so I thought this list was the best choice. Tell me if there's a better place. I was working on a site developed over Zope 2.10, using python 2.4 and a Debian Etch (ask me if you need more informations). Sometimes, at non-predictable times (I think, when concurrent accesses are performed, because of the nature of the error), I get this backtrace [ in http://codepad.org/cM76kVjT too ]: Site Error An error was encountered while publishing this resource. AssertionError Sorry, a site error occurred. Traceback (innermost last): Module ZPublisher.Publish, line 202, in publish_module_standard Module Products.Localizer.patches, line 89, in new_publish Module ZPublisher.Publish, line 150, in publish Module Zope2.App.startup, line 221, in zpublisher_exception_hook Module ZPublisher.Publish, line 79, in publish Module zope.security.management, line 85, in newInteraction AssertionError: newInteraction called while another interaction is active: File "/usr/lib/zope2.10/lib/python/ZServer/PubCore/ ZServerPublisher.py", line 25, in __init__ response=b) File "/usr/lib/zope2.10/lib/python/ZPublisher/Publish.py", line 401, in publish_module environ, debug, request, response) File "/usr/lib/zope2.10/lib/python/ZPublisher/Publish.py", line 202, in publish_module_standard response = publish(request, module_name, after_list, debug=debug) File "/var/lib/zope2.10/instance/oldrevision/Products/Localizer/ patches.py", line 89, in new_publish File "/usr/lib/zope2.10/lib/python/ZPublisher/Publish.py", line 79, in publish newInteraction() File "/usr/lib/zope2.10/lib/python/zope/security/management.py", line 91, in newInteraction interaction._newInteraction_called_from = traceback.extract_stack() (Also, the following error occurred while attempting to render the standard error message, please see the event log for full details: name 'PARENTS' is not defined) -------------------------------------------------------------------------------- Troubleshooting Suggestions The URL may be incorrect. The parameters passed to this resource may be incorrect. A resource that this resource relies on may be encountering an error. For more detailed information about the error, please refer to the error log. If the error persists please contact the site maintainer. Thank you for your patience. It seems that two concurrent "interactions" were performed. I'm not so much in the inner workings of Zope, especially not for the exact semantic of "interaction", so I may be going around in circles, but I tried looking at the newInteraction / endInteraction implementations, which simply check for concurrent interactions not to happen (otherwise, throw the above AssertionError). What I miss is: who prevents such concurrent interactions to happen? I saw nowhere in the code such a critical section, so it's obvious that sooner or later two requests, especially for busy sites, happen concurrently and this error is generated. Thank you in advance for any hint. -- Mattia "RedGlow" Belletti http://thick.foschia.info - http://anacrusi.splinder.com

2 1

Zope 2.11.0c1 released
by Andreas Jung 26 May '08

26 May '08

Hi, I just released Zope 2.11.0c1 in order to get the final release of 2.11.0 out of the door as soon as possible: <http://www.zope.org/Products/Zope/2.11.0c1> This releases contains the latest official Zope 3.4.0 codebase. I plan to release Zope 2.11.0 final in roughly three weeks from now (around June 14th). Andreas

3 4

Zope Tests: 4 OK, 1 Failed
by Zope Tests Summarizer 25 May '08

25 May '08

Summary of messages to the zope-tests list. Period Sat May 24 11:00:00 2008 UTC to Sun May 25 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Test failures ------------- Subject: FAILED (failures=1) : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat May 24 21:06:07 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009604.html Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Sat May 24 21:00:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009600.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat May 24 21:01:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009601.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sat May 24 21:03:06 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009602.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat May 24 21:04:37 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009603.html

1 0

Re: SVN: Products.ZopeVersionControl/trunk/ Purge old zope2 Interface interfaces for Zope 2.12 compatibility.
by Tres Seaver 25 May '08

25 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dieter Maurer wrote: > Tres Seaver wrote at 2008-5-23 17:54 -0400: >> ... >> It provides the Z2 interfaces or *backward compatibilty*: those >> interfaces never worked for component dispatch (which makes them useless >> for their major purpose), and the various places in the Zope2 code which >> attempted to allow "sniffing" them were crufty bug magnets. >> >> Encouraging people to take another year ripping them out is silly. > > It is the agreed upon policy: step 1 we deprecate the feature > and issue deprecation warings indicating when the feature will go > away; step 2 we remove the feature. > > Why do you not have introduced the deprecation warnings years ago? > Do it now at least for Zope 2.11 as you have already removed > the code on the trunk. Done: http://svn.zope.org/Zope/branches/2.11/?rev=86939&view=rev Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIOPl8+gerLs4ltQ4RAqfLAJ9S7a/Uxhw+L9ECRy/erJ57fBlidQCgx1JX FRI1z2B5DiMIqoiM6T299tE= =koMz -----END PGP SIGNATURE-----

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 24 May '08

24 May '08

Summary of messages to the zope-tests list. Period Fri May 23 11:00:00 2008 UTC to Sat May 24 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Fri May 23 21:00:12 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009595.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri May 23 21:01:43 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009596.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri May 23 21:03:13 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009597.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri May 23 21:04:43 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009598.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri May 23 21:06:13 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009599.html

1 0

Re: [Zope-dev] Zope and Storm (SQL)
by Jürgen kartnaller 24 May '08

24 May '08

On Sat, May 24, 2008 at 11:28 AM, Andreas Jung <lists(a)zopyx.com> wrote: > > > --On 24. Mai 2008 10:47:54 +0200 Jürgen kartnaller < > juergen.kartnaller(a)gmail.com> wrote: > > There seems to be some interest on the use of SQL databases with Zope. >> >> Lovelysystems is now using SQL databases as the primary storage for their >> applications. We use Zope and Postgres with Storm as ORM. >> The main reason for switching to SQL database were speed issues with >> queries. >> >> > Thanks for this interesting mail. > > Some questions: > > - how to you deal with binary large objects? z3c.extfile > > > - how do you deal with changes in the data model and > related migrations? Our SQL-Scripts contain alter-table to update existing tables. > > > - how do you deal with hierarchical or semi-structured data > (e.g. SGML, XML)? We have no use case for this right now. Jürgen

1 0

Re: SVN: Products.ZopeVersionControl/trunk/ Purge old zope2 Interface interfaces for Zope 2.12 compatibility.
by Tres Seaver 24 May '08

24 May '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wichert Akkerman wrote: > Previously Laurence Rowe wrote: >> Log message for revision 86849: >> Purge old zope2 Interface interfaces for Zope 2.12 compatibility. > > This change, and other, do something very dangerous: they replace the > Zope2 interface with a Zope2 interface under the exact same name and > location. This is bad: it wrongly makes people thing their code keeps > working while they are now suddenly doing things like putting Z3 > interfaces in __implements__ tuples and silently changes calling > conventions. > > If you make such changes please make sure to either change the interface > name or only have it importable from another location. - -1. Anybody who still has '__implements__' in their code needs to rip it out immediately, replacing it with the equivalent Z3 idioms. Lots of code has *both* idoms, which is just silly in this day and age: the Z2 interfaces have been worthless for three years now (since Five landed in the Z2 core in April 2005. Plone is already going to have to do this to work with CMF trunk, because the "bridge" code which provided BBB Z2 interfaces is now gone. I note with some frustration that ripping the Z2 interfaces out of Plone code was slated to be done during the goldegg project, which closed two years ago, with most of the work done in fall 2005. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver(a)palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFINX7F+gerLs4ltQ4RAhRYAJ4nKgW45zjL7Sta0DwhD4HPLi3yrgCfaXnA gIynXQMjqwbyAXOwuiml+Bc= =x/Sa -----END PGP SIGNATURE-----

3 8

Five registerPackage results in unresolved ConflictError
by Sasha Vincic 23 May '08

23 May '08

Hi On a server we have a ZEO server with 6 clients. When we start/restart the server we often get on random instance an AttributeError @@plone and all other browser pages. I have tracked it down to a ConflictError when installing Five on startup. See traceback bellow. To solve this I tried to set enable-product-installation = off to all except one instance but I still got errors. For now we restart the broken instances until they work, I have tried to set sleeping times up to couple seconds between the instances but it didn't make any difference. Five fails when it tries to execute the registerPackage in zcml files. Not the same product every time. First I thought it didn't respect the enable-product-instalation but that is checked in App.Product.initializeProduct method. So I played in fiveconfigure.py with transaction.savepoint() but no success but if I manually check App.Product.doInstall like in the diff below Now my question is if this is correct solution for the problem or will it have other side effects that I am not aware of? How do I write tests for an ConflicError during startup? /Sasha Index: fiveconfigure.py =================================================================== --- fiveconfigure.py (revision 86781) +++ fiveconfigure.py (working copy) @@ -23,7 +23,7 @@ import warnings import App.config -from App.Product import initializeProduct +from App.Product import initializeProduct, doInstall from App.ProductContext import ProductContext import Products from zLOG import LOG, ERROR @@ -265,6 +265,8 @@ if not hasattr(module_, '__path__'): raise ValueError("Must be a package and the " \ "package must be filesystem based") + if not doInstall(): + return app = Zope2.app() try: 2008-05-16 11:48:17 ERROR Zope Couldn't install Five Traceback (most recent call last): File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/OFS/Application.py", line 783, in install_product initmethod(context) File "/Users/sasha/Development/eea-buildout-clean/products/Five/__init__.py", line 31, in initialize zcml.load_site() File "/Users/sasha/Development/eea-buildout-clean/products/Five/zcml.py", line 41, in load_site _context = xmlconfig.file(file) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/zope/configuration/xmlconfig.py", line 560, in file context.execute_actions() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/zope/configuration/config.py", line 612, in execute_actions callable(*args, **kw) File "/Users/sasha/Development/eea-buildout-clean/products/Five/fiveconfigure.py", line 285, in _registerPackage transaction.commit() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/transaction/_manager.py", line 96, in commit return self.get().commit(sub, deprecation_wng=False) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/transaction/_transaction.py", line 380, in commit self._saveCommitishError() # This raises! File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/transaction/_transaction.py", line 378, in commit self._commitResources() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/transaction/_transaction.py", line 433, in _commitResources rm.commit(self) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/ZODB/Connection.py", line 484, in commit self._commit(transaction) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/ZODB/Connection.py", line 518, in _commit raise ConflictError(object=obj) ConfigurationExecutionError: ZODB.POSException.ConflictError: database conflict error (oid 0x28f61f, class App.Product.Product) in: File "/Users/sasha/Development/eea-buildout-clean/src/plone.session/plone/session/configure.zcml", line 5.4-5.65 <five:registerPackage package="." initialize=".initialize" /> Traceback (most recent call last): File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/Zope2/Startup/run.py", line 56, in ? run() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/Zope2/Startup/run.py", line 21, in run starter.prepare() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/Zope2/Startup/__init__.py", line 98, in prepare self.startZope() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/Zope2/Startup/__init__.py", line 257, in startZope Zope2.startup() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/Zope2/__init__.py", line 47, in startup _startup() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/Zope2/App/startup.py", line 103, in startup OFS.Application.initialize(application) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/OFS/Application.py", line 304, in initialize initializer.initialize() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/OFS/Application.py", line 333, in initialize self.install_products() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/OFS/Application.py", line 605, in install_products return install_products(app) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/OFS/Application.py", line 636, in install_products folder_permissions, raise_exc=debug_mode) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/OFS/Application.py", line 783, in install_product initmethod(context) File "/Users/sasha/Development/eea-buildout-clean/products/Five/__init__.py", line 31, in initialize zcml.load_site() File "/Users/sasha/Development/eea-buildout-clean/products/Five/zcml.py", line 41, in load_site _context = xmlconfig.file(file) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/zope/configuration/xmlconfig.py", line 560, in file context.execute_actions() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/zope/configuration/config.py", line 612, in execute_actions callable(*args, **kw) File "/Users/sasha/Development/eea-buildout-clean/products/Five/fiveconfigure.py", line 285, in _registerPackage transaction.commit() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/transaction/_manager.py", line 96, in commit return self.get().commit(sub, deprecation_wng=False) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/transaction/_transaction.py", line 380, in commit self._saveCommitishError() # This raises! File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/transaction/_transaction.py", line 378, in commit self._commitResources() File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/transaction/_transaction.py", line 433, in _commitResources rm.commit(self) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/ZODB/Connection.py", line 484, in commit self._commit(transaction) File "/Users/sasha/Development/eea-buildout-clean/parts/zope2/lib/python/ZODB/Connection.py", line 518, in _commit raise ConflictError(object=obj) zope.configuration.config.ConfigurationExecutionError: ZODB.POSException.ConflictError: database conflict error (oid 0x28f61f, class App.Product.Product) in: File "/Users/sasha/Development/eea-buildout-clean/src/plone.session/plone/session/configure.zcml", line 5.4-5.65 <five:registerPackage package="." initialize=".initialize" />

6 9

Zope Tests: 5 OK
by Zope Tests Summarizer 23 May '08

23 May '08

Summary of messages to the zope-tests list. Period Thu May 22 11:00:00 2008 UTC to Fri May 23 11:00:00 2008 UTC. There were 5 messages: 5 from Zope Tests. Tests passed OK --------------- Subject: OK : Zope-2.8 Python-2.3.6 : Linux From: Zope Tests Date: Thu May 22 21:05:48 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009590.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu May 22 21:07:18 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009591.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu May 22 21:08:48 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009592.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu May 22 21:10:19 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009593.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu May 22 21:11:49 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-May/009594.html

1 0