Re: [Zope-dev] zope.sendmail and critical transaction errors.
Tres Seaver wrote: Patches attached for comment. - -sys.maxint to changing the mail delivery to a non-transactional form. Switching to a before commit hook is the *worst* of the optoins: it defeats the whole point of using zope.sendmail in the first place, which was to avoidi multiple e-mails on retried requests: if the application doesn't want the mail to be transactional, then it should just send it immediately (which is what the MailHost used to do). At that point, the user would get an error screen, which couold only be cleared by the admin fixing the mail configuration. The misconfiguration of the mail host in transactional mode *does* cause the server to go into a lockdown mode (because errors are not supposed to be raised in 'tpc_finish'). There is *no* database corruption, but the transaction manager can't know that, and so it deliberately refuses to commit more transactions until the admin un-futzes the problem (in this case, by fixing the mailhost configuration) and restarts the server. Yeah, what he said... Chris -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk ___ 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.sendmail and critical transaction errors.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/24/10 09:30 , Chris Withers wrote: Tres Seaver wrote: The misconfiguration of the mail host in transactional mode *does* cause the server to go into a lockdown mode (because errors are not supposed to be raised in 'tpc_finish'). There is *no* database corruption, but the transaction manager can't know that, and so it deliberately refuses to commit more transactions until the admin un-futzes the problem (in this case, by fixing the mailhost configuration) and restarts the server. Yeah, what he said... It's not as easy as that, though. Mailhost misconfiguration is just one reason why errors may be raised during the actual sending. The receiver address may be wrong, which is where I tend to see it. This is not a condition I could reasonably test for in my code before attempting to send though the MailHost. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAkwjDWUACgkQRAx5nvEhZLKf9ACgjfp7Nxf5B+2BwT6Egp6mhuVV yGIAoKhuD8sEGT+mn6NcbTvqlWxduYsi =LIL8 -END PGP SIGNATURE- ___ 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.sendmail and critical transaction errors.
On 6/24/10 09:46 , Jens Vagelpohl wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 6/24/10 09:30 , Chris Withers wrote: Tres Seaver wrote: The misconfiguration of the mail host in transactional mode *does* cause the server to go into a lockdown mode (because errors are not supposed to be raised in 'tpc_finish'). There is *no* database corruption, but the transaction manager can't know that, and so it deliberately refuses to commit more transactions until the admin un-futzes the problem (in this case, by fixing the mailhost configuration) and restarts the server. Yeah, what he said... It's not as easy as that, though. Mailhost misconfiguration is just one reason why errors may be raised during the actual sending. The receiver address may be wrong, which is where I tend to see it. This is not a condition I could reasonably test for in my code before attempting to send though the MailHost. What might be interesting is a MailHost for non-bulk mail sending which does the SMTP HELO/MAIL FROM/RCPT TO bits immediately and only delays the DATA command until transaction commit time. That will allow you to detect almost all SMTP configuration problems and address errors in your code while still getting transaction support. Personally I've updated all my code to sending mail directly and not using zope.sendmail. Being able to catch and handle errors is much more useful to me than preventing extremely rare duplicate emails. Wichert. ___ 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-dev] Zope Tests: 31 OK, 3 Failed
Summary of messages to the zope-tests list. Period Wed Jun 23 12:00:00 2010 UTC to Thu Jun 24 12:00:00 2010 UTC. There were 34 messages: 6 from Zope Tests, 11 from ccomb at free.fr, 1 from ct at gocept.com, 16 from jdriessen at thehealthagency.com. Test failures - Subject: FAILED: Repository policy check found errors in 422 projects From: ct at gocept.com Date: Wed Jun 23 21:14:21 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015655.html Subject: FAILED : ZTK 1.0dev / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Thu Jun 24 00:09:15 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015665.html Subject: FAILED : Zope Buildbot / ztk_win slave-win From: jdriessen at thehealthagency.com Date: Thu Jun 24 07:23:38 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015679.html Tests passed OK --- Subject: OK : Zope Buildbot / zope2.12 slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 23 08:55:41 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015652.html Subject: OK : Zope Buildbot / zope2 slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 23 09:03:32 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015653.html Subject: OK : Zope Buildbot / ztk slave-osx From: jdriessen at thehealthagency.com Date: Wed Jun 23 09:32:50 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015654.html Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Wed Jun 23 21:29:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015656.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Wed Jun 23 21:31:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015657.html Subject: OK : Zope-2.12 Python-2.6.5 : Linux From: Zope Tests Date: Wed Jun 23 21:33:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015658.html Subject: OK : Zope-2.12-alltests Python-2.6.5 : Linux From: Zope Tests Date: Wed Jun 23 21:35:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015659.html Subject: OK : Zope-trunk Python-2.6.5 : Linux From: Zope Tests Date: Wed Jun 23 21:37:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015660.html Subject: OK : Zope-trunk-alltests Python-2.6.5 : Linux From: Zope Tests Date: Wed Jun 23 21:39:22 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015661.html Subject: OK : BlueBream template / Python2.4.6 32bit linux From: ccomb at free.fr Date: Wed Jun 23 22:00:55 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015664.html Subject: OK : BlueBream template / Python2.5.2 32bit linux From: ccomb at free.fr Date: Wed Jun 23 22:00:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015663.html Subject: OK : BlueBream template / Python2.6.4 32bit linux From: ccomb at free.fr Date: Wed Jun 23 22:00:57 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015662.html Subject: OK : ZTK 1.0dev / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Thu Jun 24 00:10:12 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015666.html Subject: OK : ZTK 1.0dev / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Thu Jun 24 00:10:28 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015667.html Subject: OK : Zope 3.4.1 KGS / Python2.4.6 32bit linux From: ccomb at free.fr Date: Thu Jun 24 00:30:08 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015668.html Subject: OK : Zope 3.4.1 KGS / Python2.5.2 32bit linux From: ccomb at free.fr Date: Thu Jun 24 00:53:18 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015669.html Subject: OK : ZTK 1.0 / Python2.4.6 Linux 32bit From: ccomb at free.fr Date: Thu Jun 24 01:45:47 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015670.html Subject: OK : ZTK 1.0 / Python2.6.4 Linux 32bit From: ccomb at free.fr Date: Thu Jun 24 01:45:58 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015671.html Subject: OK : ZTK 1.0 / Python2.5.2 Linux 32bit From: ccomb at free.fr Date: Thu Jun 24 01:46:06 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015672.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Thu Jun 24 05:55:10 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015673.html Subject: OK : Zope Buildbot / zope2.12 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Thu Jun 24 05:55:20 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015674.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu64 From: jdriessen at thehealthagency.com Date: Thu Jun 24 05:57:05 EDT 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-June/015675.html Subject: OK : Zope Buildbot / zope2 slave-ubuntu32 From: jdriessen at thehealthagency.com Date: Thu Jun 24
[Zope-dev] check_python_version in Zope 2.12.7
Hello, There is a nice (and yet useless) python version check done in Zope2.Startup to verify that you have at least Python 2.3.4 when the daemon start. I guess it's a bit outdated in Zope2 2.12.7 (this version). Regards, Sylvain, -- Sylvain Viollon -- Infrae t +31 10 243 7051 -- http://infrae.com Hoevestraat 10 3033GC Rotterdam -- The Netherlands ___ 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] check_python_version in Zope 2.12.7
Hi. On Thu, Jun 24, 2010 at 3:43 PM, Sylvain Viollon sylv...@infrae.com wrote: There is a nice (and yet useless) python version check done in Zope2.Startup to verify that you have at least Python 2.3.4 when the daemon start. I guess it's a bit outdated in Zope2 2.12.7 (this version). Right. I removed it from 2.12 / trunk. Thanks for noticing it :) Hanno ___ 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-dev] Zope 3.4.1 KGS released!
== Zope 3.4.1 Released! == June 22, 2010 - The Zope 3 development team announces the Zope 3.4.1 release. The 3.4.1 is the long awaited next bugfix version of 3.4.0. Major changes ~ - setuptools update to 0.6c11, so that it supports svn 1.6. - z3c.layer update to 0.2.4, which is a **SECURITY** fix. For details see the changelog. Packages and Eggs - Zope 3 is now fully converted to an egg-based system. While some work still remains, it integrates very well with the rest of the Python community. The conversion to egg-based packaging also enables other Python developers to only have to use small bits and pieces of the complete Zope software system. The conversion means that Zope 3 developers do not use the classic Zope 3 tar-ball release anymore. However, for your convenience, Zope 3 developers will provide the classic Zope 3 tar ball releases for at least the 3.4 series. So how are Zope 3 applications built using only eggs? The Known Good Set (KGS) The known good set -- or in short KGS -- is a configuration of packages and their versions that are known to work well together. The compatibility is frequently verified by running over twelve thousand tests on a daily basis [1]_. The KGS is tested against Python 2.4 and 2.5 on the 32- and 64-bit platforms. The list of controlled packages and their versions for Zope 3.4 can be found at the Zope 3 KGS site [2]_. The KGS can be used in several ways [3]_. The most common way is to nail the versions by downloading the version configuration file [4]_ and insert them as follows in your buildout configuration:: [buildout] versions = versions ... [versions] zope.interface = 3.4.0 ... ``zopeproject`` Project Builder ~~~ To start building a project using a common setup, a package called `zopeproject` can be used to quickly setup the boilerplate for the project. Ample documentation is provided at the `zopeproject` home page [5]_. `zopeproject` uses Paste or ZDaemon to create a working server. The following commands get you started:: $ easy_install zopeproject $ zopeproject HelloWorld $ cd HelloWorld $ bin/helloworld-ctl foreground Demo Packages ~ At this point, there is no demo package demonstrating a simple Zope 3 application setup. However, the ``z3c.formdemo`` package can be used as a fairly minimal setup. To get started with it, enter the following:: $ svn co svn://svn.zope.org/repos/main/z3c.formdemo/tags/1.5.3 formdemo $ cd formdemo $ python bootstrap.py $ ./bin/buildout -v $ ./bin/demo fg .. [1] http://zope3.pov.lt/buildbot .. [2] http://download.zope.org/zope3.4/3.4.1/controlled-packages.cfg .. [3] http://download.zope.org/zope3.4/intro.html .. [4] http://download.zope.org/zope3.4/3.4.1/versions.cfg .. [5] http://pypi.python.org/pypi/zopeproject Downloads - - Zope 3.4 KGS: http://download.zope.org/zope3.4 - Zope 3.4 Controlled Packages: http://download.zope.org/zope3.4/3.4.1/controlled-packages.cfg - Zope 3.4 Versions: http://download.zope.org/zope3.4/3.4.1/versions.cfg - The classic Zope 3 source release will be made only on request. - The Windows .exe installer will be made only on request. Installation instructions for both Windows and Un*x/Linux are now available in the top level `README.txt` file of the distribution. The binary installer is recommended for Windows. Zope 3.4 requires Python 2.4 or 2.5 to run. You must also have zlib installed on your system. Resources - - Zope 3 Development Web Site: http://wiki.zope.org/zope3 - Zope 3 Developers Mailing List: http://mail.zope.org/mailman/listinfo/zope-dev Retired: http://mail.zope.org/mailman/listinfo/zope3-dev - Zope 3 Users Mailing List: http://mail.zope.org/mailman/listinfo/zope-users - Bug tracker at launchpad: https://launchpad.net/zope3 - IRC Channel: #zope3-dev at irc.freenode.net About Zope 3 Zope 3 is a web application server that continues to build on the heritage of Zope. It was rewritten from scratch based on the latest software design patterns and the experiences of Zope 2. The component architecture is the very core of Zope 3 that allows developers to create flexible and powerful web applications. Compatibility with Zope 2 ~ Zope 3 is not upwards compatible with Zope 2. This means you cannot run Zope 2 applications in Zope 3. We continue to work on the transition from Zope 2 to Zope 3 by making Zope 2 use more and more of the Zope 3 infrastructure. This means that new code written in Zope 2 can benefit from Zope 3 technology. Also, with care, code can be written that works in both Zope 3 and Zope 2. This allows a Zope 2 application to slowly evolve towards Zope 3. Unchanged Zope 2 applications are never expected to work in Zope 3, however. About the Zope Foundation - The
[Zope-dev] ZODB Documentation Fundraising
The blog: http://zodbdocs.blogspot.com/ I am coordinating an effort to have a ZODB book written by one of our Zope clan, Carlos de la Guardia. He has completed a recent book for Packt publishing on Grok. He showed interested in writing a ZODB book if it were under Creative Commons. I have set up a blog and focused on behind-the-scenes coordination required to make the book happen. We are now at a point where: - There is an initial outline of topics to cover. - There is a way to contribute financially on the ZODB Docs Blog (through paypal). - If you can contribute to the book with written material and experience. Let me know. I will make a contributor on the blog and you can post articles. Carlos is more than happy to consolidate/pinch material (and of course give the original author credit) and put it into the final book. One of the thoughts would be to write ZODB mini-howtos/articles on the blog. Some initial ideas: transaction module (datamanagers, aftercommithook, etc), debugging scenarios (how to debug a record being mutated accidentally), conflict resolution (writing your own custom impl, btree bucket splits, etc), concurrency, any benchmarking information you have, relstorage, writing your own persistence format (keas.pbpersist?), or query strategies for ZODB. There is a lot of material to cover in this book. - There are also contribution/funding levels available which correlate to recognition of your donation in the book. That is right. Give money and you go down in history in the documentation *wink* We will have a revised outline of the book by Monday evening from Carlos. If you want to contribute material to the Blog -- let me know. You have a channel to voice your experience. More information is on the blog and will be updated as more progress is made. Again the blog is at, http://zodbdocs.blogspot.com/ -- please sign up and subscribe to the RSS feed. I am open for any feedback. I desperately want to get the larger community support and feedback early as possible. Please feel free to send comments, concerns, criticisms. cheers, alan runyan ___ 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] ZODB Documentation Fundraising
Thanks for organizing this Alan. Hopefully folks will follow your lead and contribute. Agendaless put some money into the pot today. On Thu, 2010-06-24 at 14:19 -0500, Alan Runyan wrote: The blog: http://zodbdocs.blogspot.com/ I am coordinating an effort to have a ZODB book written by one of our Zope clan, Carlos de la Guardia. He has completed a recent book for Packt publishing on Grok. He showed interested in writing a ZODB book if it were under Creative Commons. I have set up a blog and focused on behind-the-scenes coordination required to make the book happen. We are now at a point where: - There is an initial outline of topics to cover. - There is a way to contribute financially on the ZODB Docs Blog (through paypal). - If you can contribute to the book with written material and experience. Let me know. I will make a contributor on the blog and you can post articles. Carlos is more than happy to consolidate/pinch material (and of course give the original author credit) and put it into the final book. One of the thoughts would be to write ZODB mini-howtos/articles on the blog. Some initial ideas: transaction module (datamanagers, aftercommithook, etc), debugging scenarios (how to debug a record being mutated accidentally), conflict resolution (writing your own custom impl, btree bucket splits, etc), concurrency, any benchmarking information you have, relstorage, writing your own persistence format (keas.pbpersist?), or query strategies for ZODB. There is a lot of material to cover in this book. - There are also contribution/funding levels available which correlate to recognition of your donation in the book. That is right. Give money and you go down in history in the documentation *wink* We will have a revised outline of the book by Monday evening from Carlos. If you want to contribute material to the Blog -- let me know. You have a channel to voice your experience. More information is on the blog and will be updated as more progress is made. Again the blog is at, http://zodbdocs.blogspot.com/ -- please sign up and subscribe to the RSS feed. I am open for any feedback. I desperately want to get the larger community support and feedback early as possible. Please feel free to send comments, concerns, criticisms. cheers, alan runyan ___ 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-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 )
