An error occurred fetching the project authors.
- 21 May, 2013 2 commits
-
-
Kazuhiko Shiozaki authored
With this change, code like the following will use much less memory. for i in portal_catalog(...): i.activate().method() Signed-off-by: Vincent Pelletier <vincent@nexedi.com>
-
Kazuhiko Shiozaki authored
so that we can call ActivityTool.activateObject() with not only by object but also by it's path. Signed-off-by: Vincent Pelletier <vincent@nexedi.com>
-
- 22 Apr, 2013 2 commits
-
-
Julien Muchembled authored
When an object is deleted, higher level code used to flush its messages (without invoking them). However, a concurrent and very long transaction may be about to activate such an object, without conflict. We already experienced false -3 errors that could prevent other messages to be validated. Because there is no efficient and reliable way to flush absolutely all messages, messages on deleted objects are now ignored and deleted without any email notification. There's only a WARNING in logs. But for performance reasons, there's still a flush on object deletion. To simplify code, messages that went to -3 for other reasons, like a non-existing method, now go to -2. In fact, this was already the case for grouped messages. In case that a path is recycled, it may still be possible for a message to be executed on a wrong object (the new one), instead of being ignored (because the activated object was deleted). So in such scenario, developer should make sure not to delete an object that may be activated in a concurrent transaction. If the original object has an OID at the moment it is activated, an assertion will make sure the message is not executed on another object.
-
Julien Muchembled authored
-
- 18 Apr, 2013 1 commit
-
-
Julien Muchembled authored
Because flush() relies on this method, it becomes also possible to do ob.flushActivity(method_id=('immediateReindexObject', 'recursiveImmediateReindexObject'))
-
- 21 Feb, 2013 1 commit
-
-
Julien Muchembled authored
This makes code simpler, faster and easier to understand. It is easy to forget that ZODB connections can be reused by different threads, which led to bug such as the one fixed by commit 2c11b76a. ZODB already maintains a pool of connections to reuse so we don't need anymore to have one.
-
- 15 Feb, 2013 1 commit
-
-
Julien Muchembled authored
When a ZODB connection is closed, it usually returns to a ZODB pool and may be reused by another thread. If the SQL connection was open and is still in ZODB cache, the _v_database_connection attribute is still there: ActivityConnection.connect() is not called and a new instance of ZMySQLDA.db.DB is created for the new thread without initializing its sort key.
-
- 08 Jan, 2013 1 commit
-
-
Julien Muchembled authored
Messages passed to a grouping method are not sorted.
-
- 26 Nov, 2012 1 commit
-
-
Julien Muchembled authored
New SQLBase._getMessageList method has a very simple ZSQLCatalog-like API, and replaces SQL{Dict,Queue}_readMessageList DTML scripts. 'include_processing' parameter disappears (in favor of 'processing') and default behaviour is to include messages being processed.
-
- 01 Oct, 2012 1 commit
-
-
Julien Muchembled authored
If specified, <path> must be the path of an ancestor and SQLDict will merge all similar messages under this path and process only the root message. This will be used in ERP5 simulation to drop 'expand' activities that are children of other 'expand' activities. Because it can be used with grouped messages, it may be interesting to used it for recursiveImmediateReindexObject.
-
- 15 May, 2012 1 commit
-
-
Julien Muchembled authored
This is a followup to commit 8995b645 ("always start transactions with begin() and make tic() commit automatically"): there is now no need to use self.stepTic() instead of self.tic()
-
- 14 May, 2012 1 commit
-
-
Julien Muchembled authored
-
- 11 May, 2012 1 commit
-
-
Julien Muchembled authored
-
- 27 Apr, 2012 1 commit
-
-
Julien Muchembled authored
-
- 28 Dec, 2011 1 commit
-
-
Julien Muchembled authored
-
- 23 Dec, 2011 1 commit
-
-
Julien Muchembled authored
-
- 06 Dec, 2011 1 commit
-
-
Vincent Pelletier authored
Update all known callers to use the new method.
-
- 19 Oct, 2011 1 commit
-
-
Julien Muchembled authored
-
- 02 Aug, 2011 2 commits
-
-
Julien Muchembled authored
- reduce probability and cost of ConflictError by posting the activity result by activity - do not post None (to force it, it's still possible to forge an ActiveResult object containing the None value) - allow grouped messages to post results (previous implementation was not working, and this required to change the API of grouping methods)
-
Julien Muchembled authored
-
- 12 Jan, 2011 1 commit
-
-
Julien Muchembled authored
This is required for workflow scripts that are run at the end of the transaction. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42257 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 11 Jan, 2011 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@42230 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 29 Dec, 2010 1 commit
-
-
Leonardo Rochael Almeida authored
Fix test failures on testBusinessTemplate and spurious error messages on the console when trying to set the sort_key on an unconnected Connection object. Also fix the manual creation of the ActivityConnection object. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41865 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 21 Dec, 2010 1 commit
-
-
Sebastien Robin authored
ZMySQLDA connector for the activities database would finish its commit procedure before ZODB, making the description of an activity message in MySQL available before its respective data in the ZODB. The fix consisted in replacing the ZMySQLDA connector with another one based on ZMySQLDA but with a “sortKey()” method that forced it to be sorted after both the ZODB connection and the ZMySQLDA connection for ZSQLCatalog. Analysis of issue was done by Sebastien and Julien. This patch itself was done by Leonardo. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@41598 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 21 Oct, 2010 2 commits
-
-
Yoshinori Okuji authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39430 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Nicolas Dumazet authored
A lockdown can happen here when the activity can't find the waitingActivity method. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39416 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 02 Sep, 2010 1 commit
-
-
Łukasz Nowak authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@38120 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 11 Aug, 2010 3 commits
-
-
Julien Muchembled authored
Note 'distribute' method is not merged into SQLBase, for 2 reasons: - SQLQueue still differs from SQLDict because it does not remove duplicate messages. - 'order_validation_text' column only exists in 'message' table git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37687 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37686 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37683 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 20 Jul, 2010 1 commit
-
-
Leonardo Rochael Almeida authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@37189 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 15 Jul, 2010 1 commit
-
-
Sebastien Robin authored
Conflicts: bt5/erp5_base/bt/revision bt5/erp5_simulation/DocumentTemplateItem/InvoiceSimulationRule.py bt5/erp5_simulation/bt/revision bt5/erp5_trade/SkinTemplateItem/portal_skins/erp5_trade/Base_viewTradeFieldLibrary.xml bt5/erp5_trade/bt/change_log bt5/erp5_trade/bt/revision products/ERP5/Document/BusinessPath.py products/ERP5/Document/SimulationMovement.py products/ERP5/Document/TradeCondition.py products/ERP5/Document/TradeModelLine.py products/ERP5/bootstrap/erp5_mysql_innodb_catalog/bt/revision products/ERP5Type/ERP5Type.py git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@37129 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 12 May, 2010 1 commit
-
-
Sebastien Robin authored
fixed by revision 35192 (wrong sql connector used by Id tool) git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@35197 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 28 Apr, 2010 1 commit
-
-
Julien Muchembled authored
At most 1 message for a given serialization tag can be validated (cf [28706]). Respect priority/date/uid when validating only 1 message (cf [34632]). git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@34841 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 27 Apr, 2010 1 commit
-
-
Mame Coumba Sall authored
-If an exception is raised when sending mail, the error is not lost (available in zope event.log) -If an exception is raised when using the site error logger, the error is not lost. This test passes for SQLDict, but fails if activity is SQLQueue -If a traceback could not be generated, a mail can still be sent git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@34819 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 16 Apr, 2010 1 commit
-
-
Julien Muchembled authored
- When deleting duplicate messages, keep the one the highest score (priority, date, uid). - When several messages have the same serialization_tag, always validate first the one with the highest score. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@34632 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 06 Apr, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@34303 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 11 Mar, 2010 1 commit
-
-
Ivan Tyagov authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@33630 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 19 Feb, 2010 2 commits
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32882 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Julien Muchembled authored
This test does more than test_6[89]_ so it replaces them. git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@32881 20353a03-c40f-0410-a6d1-a30d3c3de9de
-