July 2008 - Zope-Dev

Zope Tests: 5 OK
by Zope Tests Summarizer 10 Jul '08

10 Jul '08

Summary of messages to the zope-tests list. Period Wed Jul 9 11:00:00 2008 UTC to Thu Jul 10 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 Jul 9 21:00:51 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009830.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 9 21:02:21 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009831.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 9 21:03:51 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009832.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 9 21:05:22 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009833.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Wed Jul 9 21:06:52 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009834.html

1 0

Dangerous shutdown procedure behaviour
by Vincent Pelletier 09 Jul '08

09 Jul '08

Hi. I think I discovered a dangerous code behaviour at zope shutdown. I've had a strange problem on a site where persistent objects are created from data inserted in an SQL table. Upon object creation, SQL table is updated to mark the line as imported. Such import got triggered just before a shutdown. After restart and another import, documents were created twice. What I believe happened (but I could not find any hard evidence of it) is that Zope blindly exited while the working thread was runing, and in the worst possible method: tpc_finish. ZODB was already commited, but mysql was not. So mysql did a rollback on changes, and the lines were in a "ready to import" state. And imported again at next import attemp. Reading shutdown code, I discovered 2 distinct timeout mechanism (note: having just one is enough to trigger the problem): - Lifetime.py: iterating through asyncore sockets, it alerts servers that it will shut down soon. If they take the veto for too long, the veto is ignored and shutdown continues. Default timeout is 20 seconds, meaning there is at most one minute from the first shutdown notice to the effective process exit (taking all runing threads down). When invoking "zopectl stop", it's runing a "fast" shutdown, which means the timeout is shortened to 1 second, so total maximum sutdown time is 3 seconds. This timeout can be worked around by just writing blocking shutdown methods and not using the veto system. - zdaemon/zdrun.py: if the instance being shut down still responds after 10 seconds, it will be sent a SIGKILL. This cannot be worked around without changing code in zdrun.py or not executing it at all (no idea if there is any alternative). I could easily reproduce the problem by writing a simple connection mamager which calls time.wait(3600) in _finish method and defining a sortKey method to make it commit after another connection manager. I could not find a trace of any mechanism preventing commit from happening when a shutdown is in progress, and I don't think there should be any: considering that some storages might be accessed through a network, latency can become a problem, so tpc_finish can take time to complete, so just checking that there is no pending shutdown before entering this function would not solve the problem. I suggest removing all those timeouts. If a user wants a Zope to shutdown for a reason serious enough to send it a SIGKILL or causing immediate python thread termination, it's his responsibility. But I think regular shutdown mechanism must not do that. Also, the same problem can happen with "zopectl fg" since Zope does not go through any shutdown sequence as far as I can tell (it just dies). -- Vincent Pelletier

1 0

Zope Tests: 5 OK
by Zope Tests Summarizer 09 Jul '08

09 Jul '08

Summary of messages to the zope-tests list. Period Tue Jul 8 11:00:00 2008 UTC to Wed Jul 9 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 Jul 8 21:09:04 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009825.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jul 8 21:10:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009826.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jul 8 21:12:05 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009827.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Tue Jul 8 21:13:35 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009828.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Tue Jul 8 21:15:05 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009829.html

1 0

Re: SVN: zope.app.container/trunk/CHANGES.txt Added release note
by Philipp von Weitershausen 09 Jul '08

09 Jul '08

Roger Ineichen wrote: > Log message for revision 88121: > Added release note > > Changed: > U zope.app.container/trunk/CHANGES.txt > > -=- > Modified: zope.app.container/trunk/CHANGES.txt > =================================================================== > --- zope.app.container/trunk/CHANGES.txt 2008-07-08 17:45:53 UTC (rev 88120) > +++ zope.app.container/trunk/CHANGES.txt 2008-07-08 17:46:50 UTC (rev 88121) > @@ -2,6 +2,13 @@ > CHANGES > ======= > > + > +Heads up: > + > +Relase zope.app.authentication 3.4.2 if this 3.6.1 get released. It contains a > +bugfix based on the BTreeContainer re-implementation. > + > + I think this it can be released now. The fix you applied was needed either way, if I'm correct. GroupFolder's __init__ was not calling its own super's __init__ but the super __init__ of BTreeFolder. This should have worked before and after the changes in zope.app.container 3.6.x. Of course, it'd be good to test this with both zope.app.container 3.5.x and 3.6.x first :)

2 1

zope.testing releases missing on pypi
by Wichert Akkerman 08 Jul '08

08 Jul '08

I see zope.testing 3.5.2 and 3.5.3 in svn and used by Zope2 but the latest version on pypi is 3.5.1. Why is that? And can that be corrected? Wichert. -- Wichert Akkerman <wichert(a)wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.

2 1

Zope Tests: 5 OK
by Zope Tests Summarizer 08 Jul '08

08 Jul '08

Summary of messages to the zope-tests list. Period Mon Jul 7 11:00:00 2008 UTC to Tue Jul 8 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: Mon Jul 7 21:01:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009820.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Mon Jul 7 21:02:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009821.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Mon Jul 7 21:04:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009822.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Mon Jul 7 21:05:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009823.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Mon Jul 7 21:07:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009824.html

1 0

Product version number redundancy with version.txt and setup.py
by Tim Hicks 08 Jul '08

08 Jul '08

Hi, Am I right in thinking that there is a duplication of information in having an eggified product's version number stored in setup.py and version.txt? Both seem to be necessary - the first for use with pypi and the second so that Zope knows what version of a product it has. The former seems more like it should be the preferred single place for this information. Does anyone have any ideas about how we might update Zope to read version information from setup.py instead? The initializeProduct function at <http://svn.zope.org/Zope/trunk/lib/python/App/Product.py?rev=73460&view=auto> seems to be the relevant place. However, I'm not sure if that code has access to the full eggy package at that stage. My guess is that the relevant object (productp?) might already have been adjusted for backward compatibility reasons at that stage. Any ideas? Tim

4 3

Zope Tests: 5 OK
by Zope Tests Summarizer 07 Jul '08

07 Jul '08

Summary of messages to the zope-tests list. Period Sun Jul 6 11:00:00 2008 UTC to Mon Jul 7 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: Sun Jul 6 21:08:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009815.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jul 6 21:09:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009816.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jul 6 21:11:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009817.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sun Jul 6 21:12:40 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009818.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sun Jul 6 21:14:10 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009819.html

1 0

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

06 Jul '08

Summary of messages to the zope-tests list. Period Sat Jul 5 11:00:00 2008 UTC to Sun Jul 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: Sat Jul 5 21:02:28 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009810.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jul 5 21:03:58 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009811.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jul 5 21:05:28 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009812.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Sat Jul 5 21:06:58 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009813.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Sat Jul 5 21:08:28 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-July/009814.html

1 0

zc.testbrowser.real support for mozlab 0.1.9
by Sebastian Wehrmann 06 Jul '08

06 Jul '08

Hi, I've checked in a branch with changes to the testbrowser.real code to make it work with mozlab 0.1.9 (and firefox 3). Could someone please review the code and inform me, if I can merge it with the trunk? The branch can be found at svn.zope.org/repos/main/zc.testbrowser/branches/sweh-mozlab0.1.9 Regards, Sebastian -- Sebastian Wehrmann · sw(a)gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 12 · fax +49 345 1229889 1 Zope and Plone consulting and development

4 5