1. 24 Aug, 2023 2 commits
    • Jérome Perrin's avatar
    • Vincent Pelletier's avatar
      CMFActivity.Activity.SQLBase: Do not increment priority after failure · 6084e852
      Vincent Pelletier authored
      When an activity failure happens, the SQL row is updated:
      - date is set to a future value, so the activity does not get retried
        immediately, in the expectation that what caused the failure may have
        cleared by that point.
      - retry is incremented, to allow limiting the total number of retries
      - priority is incremented
      
      This last point seems harder to justify, and seems redundant with the date
      increase. In the context of processing node families and with a steady
      influx of similar activities at a base priority level, such priority
      increment can postpone the victim activity execution to an arbitrarily
      large amount of time, which is undesirable.
      So, remove this increment.
      6084e852
  2. 23 Aug, 2023 2 commits
  3. 21 Aug, 2023 1 commit
  4. 18 Aug, 2023 2 commits
  5. 16 Aug, 2023 1 commit
  6. 15 Aug, 2023 3 commits
  7. 11 Aug, 2023 1 commit
  8. 10 Aug, 2023 8 commits
  9. 03 Aug, 2023 4 commits
  10. 02 Aug, 2023 2 commits
  11. 01 Aug, 2023 2 commits
  12. 28 Jul, 2023 7 commits
  13. 27 Jul, 2023 5 commits