Skip to content
Snippets Groups Projects
  1. Aug 27, 2022
  2. Aug 25, 2022
  3. Aug 19, 2022
  4. Aug 18, 2022
  5. Aug 10, 2022
  6. Aug 09, 2022
  7. Aug 08, 2022
  8. Aug 05, 2022
  9. Jul 30, 2022
  10. Jul 28, 2022
    • Lin Wenwen's avatar
      [FIX] base: serialization bug when acquiring cron · c06cee44
      Lin Wenwen authored
      
      Start Odoo with multiple cron threads (e.g. --max-cron-threads=4),
      trigger many crons at once, there is a chance one of the cron thread
      fails due to a serialization error.
      
      Inside of the `_acquire_one_job` function, the query evaluates many rows
      to find one that fit multiple requirements. Two of those requirements
      are (1) that the `nextcall` of the row is in the past or (2) that it
      exists a cron trigger for that cron with a `call_at` in the past.
      
      In case the `nextcall` of one of those rows is modified or the cron
      triggers are removed by another transaction then there can be a
      serialisation failure in the current transaction. This serialisation
      error is important, it prevents the current cron worker from acquiring a
      cron job that has been processed in another cron worker.
      
      The problem is that that postgres doesn't tell which row was modified by
      the other transaction (=processed by another worker cron) so it is not
      possible to just skip that cron and continue with the others.
      
      Our solution is to limit the WHERE clause of the `_acquire_one_job`
      function to a single row. In case there is a serialization failure we
      know the cron was processed in another job and we can skip it.
      
      Closes #96584
      
      closes odoo/odoo#96926
      
      X-original-commit: 684750a0
      Signed-off-by: default avatarJulien Castiaux <juc@odoo.com>
      Co-authored-by: default avatarJulien Castiaux <juc@odoo.com>
      c06cee44
    • Arnis Putniņš's avatar
      [CLA] Allegro IT · 7140779a
      Arnis Putniņš authored
      
      closes odoo/odoo#96790
      
      X-original-commit: 4d459050
      Signed-off-by: default avatarMartin Trigaux (mat) <mat@odoo.com>
      7140779a
  11. Jul 27, 2022
  12. Jul 21, 2022
  13. Jul 18, 2022
    • KareemAbuzaid's avatar
      [FW][FIX] crm: remove res_model/res_id from meetings when unlinking leads · 205df4df
      KareemAbuzaid authored
      
      With Calendar and CRM installed:
      - Create a lead and a meeting related to that lead.
      - Delete the lead.
      - Go to the meeting form view from the calendar App.
      - Click the Document action button and nothing will take place.
      
      After this commit if you delete the lead, you will no longer be able to the
      see the button as document information is correctly reset.
      
      Task-2917174
      Closes odoo/odoo#42450
      Closes odoo/odoo#47497
      
      closes odoo/odoo#96190
      
      X-original-commit: 71ccb7dae43a13521f2a290ce76cafd8fb5b963f
      Signed-off-by: default avatarThibault Delavallee (tde) <tde@openerp.com>
      205df4df
    • Lorenzo Ciciotti's avatar
      [FW][FIX] crm: update lead language based on partner · e0898fd4
      Lorenzo Ciciotti authored
      Onchange could also populate the lang field of the lead when updating the
      customer.
      
      Partial backport of odoo/odoo@65bb3a5710573a530939341827d1afb0f158c0ba
      
      Task-2917174
      Closes odoo/odoo#78715
      
      X-original-commit: e0e1e402a6c40ed89bc5a11671e364a67e93a176
      Part-of: odoo/odoo#96190
      e0898fd4
  14. Jul 12, 2022
  15. Jul 08, 2022
  16. Jul 01, 2022
  17. Jun 30, 2022
  18. Jun 24, 2022
  19. Jun 20, 2022
  20. Jun 17, 2022
  21. Jun 16, 2022
  22. Jun 10, 2022
  23. May 30, 2022
  24. May 20, 2022
  25. May 19, 2022
  26. May 18, 2022
  27. May 17, 2022
  28. May 12, 2022
Loading