- Zope-Dev - Zope lists

buildbot failure in Zope on zope.pagetemplate
by ct＠gocept.com 07 Jun '08

07 Jun '08

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

2 1

buildbot failure in Zope on z3c.sessionwidget
by ct＠gocept.com 07 Jun '08

07 Jun '08

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

1 0

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

07 Jun '08

Summary of messages to the zope-tests list. Period Fri Jun 6 11:00:00 2008 UTC to Sat Jun 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: Fri Jun 6 20:59:15 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009665.html Subject: OK : Zope-2.9 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 6 21:00:45 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009666.html Subject: OK : Zope-2.10 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 6 21:02:16 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009667.html Subject: OK : Zope-2.11 Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 6 21:03:46 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009668.html Subject: OK : Zope-trunk Python-2.4.4 : Linux From: Zope Tests Date: Fri Jun 6 21:05:17 EDT 2008 URL: http://mail.zope.org/pipermail/zope-tests/2008-June/009669.html

1 0

buildbot failure in Zope on z3c.etestbrowser
by ct＠gocept.com 07 Jun '08

07 Jun '08

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

1 0

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