1. 10 Aug, 2018 3 commits
  2. 09 Aug, 2018 3 commits
  3. 08 Aug, 2018 5 commits
  4. 07 Aug, 2018 2 commits
  5. 06 Aug, 2018 1 commit
  6. 03 Aug, 2018 6 commits
  7. 02 Aug, 2018 1 commit
  8. 01 Aug, 2018 2 commits
  9. 31 Jul, 2018 9 commits
  10. 27 Jul, 2018 2 commits
    • Sebastien Robin's avatar
      c9c876cf
    • Sebastien Robin's avatar
      simulation: solve random solving issues in a cluster environment · 924f20fa
      Sebastien Robin authored
      Before, when solving a solver, parsing sub objects of solver_process was done directly synchronously
      in solver_workflow. And we had the case where you have parallel transactions solving a solver,
      each of theses transactions see remaining solver not in solved state, but once all transaction are
      finished, all solver are solved. This could lead to the case where solver_process is never moved
      to succeeded. Instead of using serialize (which may lead to conflicts), just use activities in queue
      with a serialization tag.
      924f20fa
  11. 26 Jul, 2018 1 commit
  12. 25 Jul, 2018 2 commits
  13. 24 Jul, 2018 1 commit
  14. 19 Jul, 2018 1 commit
  15. 17 Jul, 2018 1 commit