1. 02 Sep, 2019 10 commits
  2. 30 Aug, 2019 1 commit
  3. 07 Aug, 2019 3 commits
  4. 06 Aug, 2019 2 commits
  5. 05 Aug, 2019 2 commits
  6. 02 Aug, 2019 8 commits
  7. 01 Aug, 2019 3 commits
  8. 31 Jul, 2019 2 commits
  9. 30 Jul, 2019 1 commit
  10. 29 Jul, 2019 2 commits
  11. 26 Jul, 2019 4 commits
  12. 25 Jul, 2019 2 commits
    • Vincent Pelletier's avatar
      CMFActivity.ActivityTool: Set exc_type default value. · 3123e1a9
      Vincent Pelletier authored
      This property is only conditionally set, which causes distracting error
      when something goes wrong. If we really want to check that the expected
      code path was followed there has to be a better check and a more debugging-
      friendly error than an AttributeError.
      3123e1a9
    • Vincent Pelletier's avatar
      CMFActivity.Activity.SQLBase: Tolerate group_id set without a grouping_method_id. · e80c4f06
      Vincent Pelletier authored
      While such activity parameter combination does not make sense, it is
      technically possible to spawn activities with a group_id set but without a
      grouping_method_id.
      The consequence is zombie activities: they never fail, do not prevent other
      activities from being executed, but and are permanently run on the node
      which reserved more than one because:
      - all but one activity is in MESSAGE_NOT_EXECUTED state, forcing an abort
      - finalizeMessageExecution does not understand that MESSAGE_NOT_EXECUTED
        activities may not have failed, and itself fail while trying to detect
        the failure type (ConflictError vs. others), failing to free & postpone
        the activity, in turn failing to bring it to eventually permanent failure
        state.
      Make those conditions consistent, and use tuple-unpacking to detect any
      future inconsistency much earlier, simplifying debugging.
      e80c4f06