[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Tue Feb 23 12:00:00 2010 UTC to Wed Feb 24 12:00:00 2010 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 23 20:36:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013623.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Feb 23 20:38:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013624.html Subject: OK : Zope-2.12 Python-2.6.4 : Linux From: Zope Tests Date: Tue Feb 23 20:40:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013625.html Subject: OK : Zope-2.12-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Feb 23 20:42:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013626.html Subject: OK : Zope-trunk Python-2.6.4 : Linux From: Zope Tests Date: Tue Feb 23 20:44:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013627.html Subject: OK : Zope-trunk-alltests Python-2.6.4 : Linux From: Zope Tests Date: Tue Feb 23 20:46:13 EST 2010 URL: http://mail.zope.org/pipermail/zope-tests/2010-February/013628.html ___ 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] exception views lost context on Zope 2.12
On 23.02.10 13:36, Wichert Akkerman wrote: On 2/23/10 13:22 , Martin Aspeli wrote: Wichert Akkerman wrote: It is not useful, it is critical. Without the context you can not use any browser views for example. Well, the use cases that have been to date have done without it. :) I'm not disagreeing with you, I'm just saying we need to make sure we don't break existing use cases (plone.app.linkintegrity, plone.caching to name two that I know of). As I said plone.app.linkintegrity always used this trick in Zope 2.10, so it is not something I just came up with. It is known to work :) wichert is right, the existing use cases — or say, at least p.a.linkintegrity — have _not_ done without it. in fact, the confirmation view (i.e. you really wanna delete this?) relies on the (acquisition) context. otherwise it could never be rendered as something that looks like a regular page. however, the monkey patch used here is only partly applied for zope 2.12, and the bit where the view gets aq-wrapped is not[*]. since it remains to work, though, i suspect that wichert's problem could be something else... andi [*] see http://dev.plone.org/plone/browser/plone.app.linkintegrity/trunk/plone/app/linkintegrity/monkey.py#L18 -- zeidler it consulting - http://zitc.de/ - i...@zitc.de friedelstraße 31 - 12047 berlin - telefon +49 30 25563779 pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/ plone 4.0 alpha released! -- http://plone.org/products/plone/ ___ 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] unable to acquire commit lock
few days ago my I'm getting this errors when trying logging on /manage, googling I don't found any reasonable solution and/or information about, only thing was, restarting zope instances works, thats true Traceback: 2010-02-24T09:43:09 ERROR Zope.SiteErrorLog http://www.mywebsite.com/login_form Traceback (innermost last): Module ZPublisher.Publish, line 125, in publish Module Zope2.App.startup, line 238, in commit Module transaction._manager, line 96, in commit Module transaction._transaction, line 395, in commit Module transaction._transaction, line 498, in _commitResources Module ZODB.Connection, line 726, in tpc_vote Module relstorage.relstorage, line 711, in tpc_vote Module relstorage.relstorage, line 686, in _vote Module relstorage.relstorage, line 593, in _prepare_tid Module relstorage.adapters.mysql, line 506, in start_commit Module relstorage.adapters.mysql, line 672, in _hold_commit_lock StorageError: Unable to acquire commit lock I looked at the code and this function _hold_commit_lock has the following SELECT statement: SELECT GET_LOCK(CONCAT(DATABASE(), '.commit'), %s) I tried to reproduce it querying manually but it looks like an unknown command, and other point, I don't know what Zope put in %s variable. Does anybody already had this problem? Thanks for any reply. Regards, - - iarlyy selbir | ski0s :wq! ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] unable to acquire commit lock
Just a guess, but it looks like you are trying to get a transaction lock on a mysql table, so does the mysql table you are using have a storage engine that supports transactions (eg. InnoDB)? Jonathan From: zope-boun...@zope.org [mailto:zope-boun...@zope.org] On Behalf Of iarly selbir | ski0s Sent: February-24-10 8:12 AM To: zope@zope.org Subject: [Zope] unable to acquire commit lock few days ago my I'm getting this errors when trying logging on /manage, googling I don't found any reasonable solution and/or information about, only thing was, restarting zope instances works, thats true Traceback: 2010-02-24T09:43:09 ERROR Zope.SiteErrorLog http://www.mywebsite.com/login_form Traceback (innermost last): Module ZPublisher.Publish, line 125, in publish Module Zope2.App.startup, line 238, in commit Module transaction._manager, line 96, in commit Module transaction._transaction, line 395, in commit Module transaction._transaction, line 498, in _commitResources Module ZODB.Connection, line 726, in tpc_vote Module relstorage.relstorage, line 711, in tpc_vote Module relstorage.relstorage, line 686, in _vote Module relstorage.relstorage, line 593, in _prepare_tid Module relstorage.adapters.mysql, line 506, in start_commit Module relstorage.adapters.mysql, line 672, in _hold_commit_lock StorageError: Unable to acquire commit lock I looked at the code and this function _hold_commit_lock has the following SELECT statement: SELECT GET_LOCK(CONCAT(DATABASE(), '.commit'), %s) I tried to reproduce it querying manually but it looks like an unknown command, and other point, I don't know what Zope put in %s variable. Does anybody already had this problem? Thanks for any reply. Regards, - - iarlyy selbir | ski0s :wq! ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] unable to acquire commit lock
When using relstorage + MySQL it creates seven tables to storage all objects, following: mysql show tables; | current_object - ENGINE=InnoDB | new_oid - ENGINE=MyISAM | object_ref - ENGINE=MyISAM | object_refs_added - ENGINE=MyISAM | object_state - ENGINE=InnoDB | pack_object - ENGINE=MyISAM | pack_state - ENGINE=MyISAM | pack_state_tid - ENGINE=MyISAM | transaction - ENGINE=InnoDB As you see there are tables using both InnoDB and other using MyISAM, thats default setup relstorage do Regards, - - iarlyy selbir | ski0s :wq! On Wed, Feb 24, 2010 at 10:24 AM, Jonathan (dev101) dev...@magma.ca wrote: Just a guess, but it looks like you are trying to get a transaction lock on a mysql table, so does the mysql table you are using have a storage engine that supports transactions (eg. InnoDB)? Jonathan *From:* zope-boun...@zope.org [mailto:zope-boun...@zope.org] *On Behalf Of *iarly selbir | ski0s *Sent:* February-24-10 8:12 AM *To:* zope@zope.org *Subject:* [Zope] unable to acquire commit lock few days ago my I'm getting this errors when trying logging on /manage, googling I don't found any reasonable solution and/or information about, only thing was, restarting zope instances works, thats true Traceback: 2010-02-24T09:43:09 ERROR Zope.SiteErrorLog http://www.mywebsite.com/login_form Traceback (innermost last): Module ZPublisher.Publish, line 125, in publish Module Zope2.App.startup, line 238, in commit Module transaction._manager, line 96, in commit Module transaction._transaction, line 395, in commit Module transaction._transaction, line 498, in _commitResources Module ZODB.Connection, line 726, in tpc_vote Module relstorage.relstorage, line 711, in tpc_vote Module relstorage.relstorage, line 686, in _vote Module relstorage.relstorage, line 593, in _prepare_tid Module relstorage.adapters.mysql, line 506, in start_commit Module relstorage.adapters.mysql, line 672, in _hold_commit_lock StorageError: Unable to acquire commit lock I looked at the code and this function _hold_commit_lock has the following SELECT statement: SELECT GET_LOCK(CONCAT(DATABASE(), '.commit'), %s) I tried to reproduce it querying manually but it looks like an unknown command, and other point, I don't know what Zope put in %s variable. Does anybody already had this problem? Thanks for any reply. Regards, - - iarlyy selbir | ski0s :wq! ___ Zope maillist - Zope@zope.org https://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope-dev )
