June 2008 - Zope-Dev

buildbot failure in Zope on ZODB
by ct＠gocept.com 06 Jun '08

06 Jun '08

The Buildbot has detected a new failure of ZODB on Zope. Full details are available at: http://zopebuildbot.whq.gocept.com/ZODB/builds/122 Buildbot URL: http://zopebuildbot.whq.gocept.com/ Buildslave for this Build: local Build Reason: The Nightly scheduler named 'ZODB nightly' triggered this build Build Source Stamp: [branch ZODB/trunk] HEAD Blamelist: BUILD FAILED: failed test Logs are attached. sincerely, -The Buildbot

1 0

Conflict Errors
by David Otero Figueroa 06 Jun '08

06 Jun '08

Hello everyone, I have a couple questions related to "conflict errors". During our home page stress testing (20 concurrent users), we detected several conflict errors (see trace below), We thought these could ONLY appear when writing objects in the ZODB. 2008-05-27T18:57:53 INFO ZODB conflict error at /portal/ (26 conflicts since startup at 2008-05-27T13:37:19) I have this problems too in a not estress testing. In a simple access (2 concurrents users) I have this response: 2008-05-27T13:23:48 INFO ZODB conflict error at /portal/ (22 conflicts since startup at 2008-05-27T10:37:28) 2008-05-27T13:23:48 INFO ZODB conflict error at /portal/ (23 conflicts since startup at 2008-05-27T10:37:28) 2008-05-27T13:29:21 INFO ZODB conflict error at /portal/login_form_usuario_pwd/ (29 conflicts since startup at 2008-05-27T10:37:28) 2008-05-27T13:29:22 INFO ZODB conflict error at /portal/login_form_usuario_pwd/ (30 conflicts since startup at 2008-05-27T10:37:28) 2008-05-27T19:48:40 INFO ZODB conflict error at /portal/portal_css/Plone Default/ploneStyles5658.css (68 conflicts since startup at 2008-05-27T13:37:19) I would like to know: - Can conflict errors appear when reading objects from the ZODB? - Could conflict errors be the cause of a "spinning ZOPE" scenario? - Is there any situation where ZOPE could try to write objects when rendering an "only read" page? - How can they be solved? - Can I realize partial commits? How to? Our configuration is as follows: Apache + Pound + ZEO architecture (5 ZEO clients, 1 ZEO storage server - 650.000 ZODB objects) Thanks in advance.

5 6

SQLAlchemy (zope.sqlalchemy) integration
by Hermann Himmelbauer 06 Jun '08

06 Jun '08

Hi, Regarding to the discussion some days ago with the SQLAlchemy Zope3 integration, I still have problems with retrieving the session. I currently use a utility for the engine, which seems to work well. However, for retrieving the session, I tried to use the following pattern (many thanks to Michael Bayer, btw.): -------- database module ----------- SASession = scoped_session(sessionmaker( transactional = True, autoflush = True, extension = ZopeTransactionExtension())) def getSASession(): SASession.remove() engine = getUtility(ISAEngineUtility).getEngine() s = SASession() s.bind = engine return s -------------------------------------------- In my application, I then use getSASession() to retrieve my session. However, what I think is not that beautiful is the "s.bind = engine" part. Are there any suggestions how to improve this? Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

3 6

buildbot failure in Zope on zc.ngi
by ct＠gocept.com 06 Jun '08

06 Jun '08

The Buildbot has detected a new failure of zc.ngi on Zope. Full details are available at: http://zopebuildbot.whq.gocept.com/zc.ngi/builds/96 Buildbot URL: http://zopebuildbot.whq.gocept.com/ Buildslave for this Build: local Build Reason: The Nightly scheduler named 'zc.ngi nightly' triggered this build Build Source Stamp: [branch zc.ngi/trunk] HEAD Blamelist: BUILD FAILED: failed test Logs are attached. sincerely, -The Buildbot

1 0

fast_listen -> fast-listen for 2.11
by Stefan H. Holek 06 Jun '08

06 Jun '08

I'd like to sneak the following patch into 2.11 before final. The idea is that zope.conf option names should use dashes and not underscores. The downside is that it will break all zope.conf files that already use this option. Objections? Stefan + Bugs Fixed + + - Fixed against-the-rules zope.conf option 'fast_listen' to read + 'fast-listen' (dash, not underscore). + Zope 2.11 rc 1 (2008/05/08) Bugs Fixed Index: skel/etc/zope.conf.in =================================================================== --- skel/etc/zope.conf.in (revision 84838) +++ skel/etc/zope.conf.in (working copy) @@ -975,8 +975,7 @@ # # To defer the opening of the HTTP socket until the end of the # startup phase: - # fast_listen false - # + # fast-listen off </http-server> # Examples: Index: lib/python/ZServer/component.xml =================================================================== --- lib/python/ZServer/component.xml (revision 84838) +++ lib/python/ZServer/component.xml (working copy) @@ -19,10 +19,10 @@ receive WebDAV source responses to GET requests. </description> </key> - <key name="fast_listen" datatype="boolean" default="on"> + <key name="fast-listen" datatype="boolean" default="on"> <description> - Defines wether the http server should listen to requests immediately - or only after zope is ready to run + Defines whether the HTTP server should listen for requests + immediately or only after Zope is ready to run. </description> </key> <key name="use-wsgi" datatype="boolean" default="off" /> -- Anything that, in happening, causes something else to happen, causes something else to happen. --Douglas Adams

2 3

Zope Tests: 5 OK
by Zope Tests Summarizer 06 Jun '08

06 Jun '08

Summary of messages to the zope-tests list. Period Thu Jun 5 11:00:00 2008 UTC to Fri Jun 6 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 Jun 5 21:07:31 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009660.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jun 5 21:09:02 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009661.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jun 5 21:10:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009662.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Thu Jun 5 21:12:02 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009663.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Thu Jun 5 21:13:32 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009664.html

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 05 Jun '08

05 Jun '08

Summary of messages to the zope-tests list. Period Wed Jun 4 11:00:00 2008 UTC to Thu Jun 5 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: Wed Jun 4 21:00:48 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009655.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jun 4 21:02:18 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009656.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jun 4 21:03:48 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009657.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jun 4 21:05:18 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009658.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed Jun 4 21:06:48 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009659.html

1 0

Deciphering Zope Comments
by Shane Hathaway 05 Jun '08

05 Jun '08

Hi all, I'm trying to get a handle on Zope 3. I plan to take a bunch of Zope 3 modules and combine them in a new way. The goal is to create for myself a comfortable working environment that lets me run simple code in a small mod_wsgi environment with easy reloading and no ZODB initially. To achieve this, I need to understand what's going on in the Zope 3 code base. While the code itself is easy to understand, there are many comments in the code that suggest changes are coming soon. Please help me figure out what is meant by these comments. The first cryptic comment comes from zope.component. The _api module starts with this gem: # SiteManager API. This needs to get deprecated eventually. But... um... everything in the module uses getSiteManager(). The whole component foundation is built on it. When is it going to be replaced? With what? By whom? I'm assuming for the moment that the comment is a lie, and that getSiteManager() is not going away, since otherwise I have no foundation to build upon. I think I want to use a threading.local as my site manager. That way, I can use a different configuration for each WSGI app even if several apps run in different threads of a single Python interpreter. It looks like the zope.app.component.hooks module does something like what I want, but that module is complicated and lacks comments in the places that matter, so I'm not quite sure what it accomplishes. I'll add comments to that module if anyone can explain it fully. That led me to the zope.thread module, which is apparently deprecated already, yet zope.app.component still depends on it. Is that an hysterical accident? Shane

6 6

Zope Tests: 5 OK
by Zope Tests Summarizer 04 Jun '08

04 Jun '08

Summary of messages to the zope-tests list. Period Tue Jun 3 11:00:00 2008 UTC to Wed Jun 4 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: Tue Jun 3 20:54:15 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009650.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jun 3 20:55:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009651.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jun 3 20:57:17 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009652.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jun 3 20:58:47 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009653.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Tue Jun 3 21:00:17 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009654.html

1 0

Strange serializing error when commiting
by Hermann Himmelbauer 03 Jun '08

03 Jun '08

Hi, In my zope3 tests, I set up some basic test data. After that, I'm calling transaction.commit(). However, I get the following traceback: --------------- snip ------------------- Error in test /home/dusty/prog/zope3-inst/lib/python/zbsp/tests/../auth.txt Traceback (most recent call last): File "/local/home/dusty/python/Python-2.4.4/lib/python2.4/unittest.py", line 251, in run self.setUp() File "/local/home/dusty/Zope-3.4.0c1/lib/python/zope/testing/doctest.py", line 2283, in setUp self._dt_setUp(test) File "/local/home/dusty/Zope-3.4.0c1/lib/python/zope/app/testing/functional.py", line 739, in setUp kwsetUp(test) File "/home/dusty/prog/zope3-inst/lib/python/zbsp/tests/test_doc.py", line 141, in setUp commit() File "/local/home/dusty/Zope-3.4.0c1/lib/python/transaction/_manager.py", line 93, in commit return self.get().commit() File "/local/home/dusty/Zope-3.4.0c1/lib/python/transaction/_transaction.py", line 325, in commit self._commitResources() File "/local/home/dusty/Zope-3.4.0c1/lib/python/transaction/_transaction.py", line 424, in _commitResources rm.commit(self) File "/local/home/dusty/Zope-3.4.0c1/lib/python/ZODB/Connection.py", line 541, in commit self._commit(transaction) File "/local/home/dusty/Zope-3.4.0c1/lib/python/ZODB/Connection.py", line 586, in _commit self._store_objects(ObjectWriter(obj), transaction) File "/local/home/dusty/Zope-3.4.0c1/lib/python/ZODB/Connection.py", line 613, in _store_objects p = writer.serialize(obj) # This calls __getstate__ of obj File "/local/home/dusty/Zope-3.4.0c1/lib/python/ZODB/serialize.py", line 407, in serialize return self._dump(meta, obj.__getstate__()) File "/local/home/dusty/Zope-3.4.0c1/lib/python/ZODB/serialize.py", line 416, in _dump self._p.dump(state) File "copy_reg.py", line 69, in _reduce_ex raise TypeError, "can't pickle %s objects" % base.__name__ TypeError: can't pickle module objects ------------------ snip ------------------- Does anyone know what this means and what I can do against it? Best Regards, Hermann -- hermann(a)qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7

3 6