1. 08 Mar, 2023 29 commits
  2. 07 Mar, 2023 5 commits
  3. 06 Mar, 2023 4 commits
    • Gabriel Monnerat's avatar
      erp5_stripe: Use activity to store stripe session in ERP5 · ce9ec7b6
      Gabriel Monnerat authored
      Creating Stripe Payment Session and HTTP Exchange in the same transaction can raise conflict errors and when it happens, we already created the session on the Stripe side.
      
      With this, when this happens, we receive one useless webhook to inform that the session has expired.
      
      Also, batch_mode was removed because we only use it in tests. The tests were updated to use like in production.
      
      This change will probably avoid the issue below:
      
      ```
      ------
      2023-03-01 13:03:33,503 INFO Tracking queuing message: activity=SQLDict, object_path=/erp5/stripe_payment_session_module/20230301-1B990F0, method_id=immediateReindexObject, args=(), kw={}, activity_kw={'group_id': '', 'serialization_tag': '/erp5/stripe_payment_session_module/20230301-1B990F0', 'alternate_method_id': 'alternateReindexObject', 'group_method_id': 'portal_catalog/catalogObjectList'}, user_name=...
      ------
      2023-03-01 13:03:33,516 INFO Tracking queuing message: activity=SQLDict, object_path=/erp5/system_event_module/20230301-9DDE8DD8, method_id=immediateReindexObject, args=(), kw={}, activity_kw={'group_id': '', 'serialization_tag': '/erp5/system_event_module/20230301-9DDE8DD8', 'alternate_method_id': 'alternateReindexObject', 'group_method_id': 'portal_catalog/catalogObjectList'}, user_name=...
      ------
      2023-03-01 13:03:33,549 INFO ZPublisher.Conflict ReadConflictError at ......_startStripePaymentSession: database read conflict error (oid 0x06be91ef, serial this txn started with 0x03eec0ca6bdaf611 2023-03-01 10:50:25.278590, serial currently committed 0x03eec0d78f096a55 2023-03-01 11:03:33.524245) (12 conflicts (0 unresolved) since startup at Tue Jan 17 03:21:57 2023)
      ------
      2023-03-01 13:03:35,057 INFO Tracking queuing message: activity=SQLDict, object_path=/erp5/stripe_payment_session_module/20230301-1E233DB, method_id=immediateReindexObject, args=(), kw={}, activity_kw={'group_id': '', 'serialization_tag': '/erp5/stripe_payment_session_module/20230301-1E233DB', 'alternate_method_id': 'alternateReindexObject', 'group_method_id': 'portal_catalog/catalogObjectList'}, user_name=...
      ------
      2023-03-01 13:03:35,066 INFO Tracking queuing message: activity=SQLDict, object_path=/erp5/system_event_module/20230301-5C3B7E3, method_id=immediateReindexObject, args=(), kw={}, activity_kw={'group_id': '', 'serialization_tag': '/erp5/system_event_module/20230301-5C3B7E3', 'alternate_method_id': 'alternateReindexObject', 'group_method_id': 'portal_catalog/catalogObjectList'}, user_name=...
      ```
      
      See merge request nexedi/erp5!1747
      ce9ec7b6
    • Kazuhiko Shiozaki's avatar
    • Kazuhiko Shiozaki's avatar
      erp5_core: remove Guard Role field in Worklist_view, as it should be defined... · 92bfa7e1
      Kazuhiko Shiozaki authored
      erp5_core: remove Guard Role field in Worklist_view, as it should be defined in predicate listbox at the bottom.
      92bfa7e1
    • Gabriel Monnerat's avatar
      erp5_stripe: Use activity to store stripe session in ERP5 · ec4a3f9d
      Gabriel Monnerat authored
      Creating Stripe Payment Session and HTTP Exchange in the same transaction can raise conflict errors and when it happens, we already created the session on the Stripe side.
      
      With this, when this happens, we receive one useless webhook to inform that the session has expired.
      
      Also, batch_mode was removed because we only use it in tests. The tests were updated to use like in production.
      ec4a3f9d
  4. 05 Mar, 2023 1 commit
  5. 03 Mar, 2023 1 commit
    • Jérome Perrin's avatar
      ui_test: ignore errors with cell/getId for testAccessUnauthorizedRelationValue · 5c40e95a
      Jérome Perrin authored
      This listbox can be used to show documents that user is not allowed to
      access, so this `cell/getId` can raise. In Zope2 it was raising
      Unauthorized and this Unauthorized was catched, on Zope4 it is raising
      NotFound, which is no longer catch since 850e436e (
      Products.ERP5Form.Form: Let NotFound exceptions propagate during
      rendering, 2022-11-25), so this NotFound was raised as a site error,
      which caused an error in the test.
      5c40e95a