1. 13 May, 2015 1 commit
  2. 06 May, 2015 1 commit
    • CMFActivity: slightly delay non-executed grouped messages · c85a840f
      When grouped messages fail, ActivityTool must distinguish 3 groups,
      in order to reexecute them separately, as follows:
      - first, those that succeeded
      - then, those that were skipped
      - at last, failed ones
      Grouping methods are updated to handle partial failures, and stop doing
      anything when something goes wrong.
      Without this, we would have the following pathological cases.
      1. Let's suppose first that skipped messages are marked as succeeded.
      The problem is that each skipped message that will fail causes the reexecution
      of those that didn't fail.
      Exemple: A:ok B:ok C:err D:err E:err F:err
        1: A:ok, B:ok, C:err, D:skipped, E:skipped, F:skipped
        2: A:ok, B:ok, D:err, E:skipped, F:skipped
        3: A:ok, B:ok, E:err, F:skipped
        4: A:ok, B:ok, F:err
        5: A:ok, B:ok -> commit
      And worst, the first failed (C) may be processable again before 5, entering
      a failing loop if it is executed again in the same group as A & B.
      2. Another implementation is to mark all skipped as failed.
        1: A:ok, B:ok, C:err, D:skipped, E:skipped, F:skipped
        2: A:ok, B:ok -> commit
        3: C:err, D:skipped, E:skipped, F:skipped
       >3: same as 3
      => D, E or F are never tried.
      Julien Muchembled committed
  3. 03 Oct, 2012 1 commit
    • Simulation: splitted expand, performance improvements and bugfixes · 5c09e2e2
      All interactions and activity tags are reviewed to fix bugs like duplicated
      root applied rules, and also reduces the amount of duplicated/useless work, e.g:
      - Simulation trees are not expanded anymore when simulated objects are modified.
      - 'expand' activities are merged (i.e. dropped) with any other 'expand' activity
        for an ancestor.
      New implementation exposes new API that hides much complexity to the developper
      about activity dependencies.
      By default, expand() now automatically defers any work if the current
      transaction takes too long time. This method also gains a parameter to
      explicitely choose when to expand, which is often important in unit tests or
      solvers. In particular, when postponing work, it takes care of setting proper
      activity dependencies.
      - If you have any code requiring to expand everything immediately, you'll have
        to replace 'expand()' by 'expand(expand_policy="immediate")'.
      - On the contrary, you should replace any 'activate().expand()' by
      expand() still accepts activity parameters for any extra needs.
      In causality workflow, 'building' state is clarified and now means
      « delivery may diverge but we can't know now ». A delivery remains in draft
      as long as it does not contain any movement built from simulation.
      After init/clone/builder/etc. scripts used to call 'startBuilding' &
      'updateCausalityState': this calls must be removed since only
      SimulatedDeliveryBuilder should take care of move to 'building' state and
      workflows now triggers 'updateCausalityState'.
      Disguised interactions have been unhardcoded and either deleted, or moved to
      appropriate interaction workflows, which have been reorganized. Those
      that triggers update of portal_workflow can be easily customized or disabled.
      New API:
      - updateSimulation() on deliveries and subscription items. It takes care of
        creating root applied rule, expanding and reindexing parts of simulation
        trees. It somehow replaces:
        - Delivery_updateSimulation
        - Delivery_updateAppliedRule
        - Delivery.applyToDeliveryRelatedMovement
        - Delivery.updateAppliedRule
        - Delivery.expand
        - Delivery.expandRuleRelatedToMovement
        - SubscriptionItem.expand
        - SubscriptionItem.updateAppliedRule
      - Delivery.localBuild() is the new way to do local building and replaces
        Delivery_expandAndBuild. Private method Delivery._localBuild replaces
      - Simulation Movements that are being built by a builder are reindexed with
        the following tag: 'built:<delivery_path>'. Any after_path_and_method_id
        dependency against 'related_simulation_movement_path_list' and reindexing
        methods should be replaced by this after_tag.
      After builder scripts used to confirm the delivery in a separate activity,
      which was useless.
      Julien Muchembled committed
  4. 06 Apr, 2012 1 commit
  5. 12 Dec, 2011 1 commit
  6. 10 Dec, 2011 1 commit
  7. 08 Dec, 2011 2 commits
  8. 06 Apr, 2011 1 commit
  9. 05 Apr, 2011 2 commits
  10. 04 Apr, 2011 1 commit
  11. 02 Aug, 2010 1 commit
  12. 03 Jun, 2010 1 commit
  13. 07 Oct, 2009 1 commit
  14. 03 Mar, 2008 1 commit
  15. 06 Nov, 2007 1 commit
  16. 03 Jan, 2007 1 commit
  17. 25 Mar, 2006 1 commit
  18. 03 Sep, 2004 1 commit
  19. 16 Feb, 2004 1 commit
  20. 08 Feb, 2004 1 commit
  21. 17 Dec, 2003 1 commit
  22. 10 Dec, 2002 1 commit