An error occurred fetching the project authors.
- 04 Oct, 2019 1 commit
-
-
Julien Muchembled authored
This is done by inheriting most of the code of ConflictFreeLog, i.e. using a doubly-linked list: - for fast iteration of the first elements, and in particular immediate access to the first element (used for creation date); - that keeps track of the history length; - that implement fast reverse iteration (although it could have been done without changing the data structure). The size of buckets is not fixed anymore to 16 items: like ConflictFreeLog, WorkflowHistoryList is also a good candidate to look at the estimated serialized size of the bucket in order to decide if elements should be added to a new one or not. Then developers won't have to care about using Pdata or not. The size is bigger than the ConflictFreeLog default, because workflow items look a lot alike and adding a few more is cheap when the ZODB compresses. No more optimized __getstate__ (except for workflow histories that have not been migrated) so BT export will be a bit more verbose. The BBB code is because of nexedi/erp5!934 /reviewed-on nexedi/erp5!941
-
- 25 Sep, 2019 1 commit
-
-
Jérome Perrin authored
When other nodes takes time to start they are not always registered when the "main" node asserts that they are there. We observed problems in an environment where resolving localhost (by DNS) takes 10 seconds. Also introduce getOtherZopeNodeList utility method that can be useful in other ZEO tests in ProcessingNodeTestCase
-
- 26 Apr, 2018 1 commit
-
-
Roque authored
- getCurrentNode method can be directly imported from CMFActivity - corresponding unittests /reviewed-on nexedi/erp5!647
-
- 10 Mar, 2015 1 commit
-
-
Gabriel Monnerat authored
-
- 10 Sep, 2013 2 commits
-
-
Arnaud Fontaine authored
ZODB Components: Revert 'Allow to execute runUnitTest for bt5 Test Components' (a771dca4) to fix tests bootstrap. The new syntax to load ZODB Tests Components is: runUnitTest BT_TITLE:TEST_NAME That commit was too adhoc as it was relying upon filesystem to load Tests Components and was not behaving like any other Components (versions was not available and other Components were not importable). At the end, it would have meant that a Test Component ran through runUnitTest and Live Tests (in ERP5 itself) would have behaved differently, thus instead: 1/ Install BT_TITLE dependencies and its test dependencies (new bt property to specify bt to be installed only for tests on a fresh instance). 2/ The site is loaded. 3/ Load the test by importing it like any other Components.
-
Arnaud Fontaine authored
-
- 03 Jan, 2013 1 commit
-
-
Julien Muchembled authored
-
- 27 Aug, 2012 1 commit
-
-
Julien Muchembled authored
-
- 16 May, 2012 1 commit
-
-
Julien Muchembled authored
This revert a wrong change in commit 8995b645
-
- 11 May, 2012 1 commit
-
-
Julien Muchembled authored
-
- 09 Aug, 2011 1 commit
-
-
Julien Muchembled authored
-
- 20 Nov, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@40430 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
- 16 Nov, 2010 1 commit
-
-
Julien Muchembled authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@40310 20353a03-c40f-0410-a6d1-a30d3c3de9de
-