Wednesday, January 26, 2022
5 changes · master
Enhancements to existing features
Email fetching now treats processing problems as reportable errors, making them easier to capture in external monitoring tools such as Sentry. This helps teams detect and respond to failed incoming email processing more reliably.
Original PR description
Description of the issue/feature this PR addresses: It you use an external system to catch warning and error like sentry, with this PR it is simple. @tde-banana-odoo it is more an error if mail cannot be processed (see last issue found recently) cc @odony -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update simplifies and standardizes how Odoo manages internal locking for shared resources such as registries and caches. It reduces duplicated code and helps make core system behavior easier to maintain without changing day-to-day user workflows.
Original PR description
It's not entirely clear whether `@synchronized` is even useful, but keep it for now. `locked` is just the default instance of `@synchronised`. - rewrite `@synchronized` using `decorator`, don't fold everything into a single call as there's a potential for parametric conflict - remove the independent `locked` in `sql_db.py` - convert `lru` to `locked` - move `Registry` over to `locked` where applicable
Calendar reminder records are now included when populating calendar data. This helps test and demonstration environments better reflect real usage, making calendar-related workflows easier to evaluate.
Original PR description
Task-2728093 See odoo/enterprise#23707
Delivery package data now includes direct links to the related sales order or warehouse picking, making shipping information easier to access. This reduces the need to pass around extra shipment details and supports cleaner delivery carrier integrations.
Original PR description
Before this commit, to access some values of the DeliveryPackage objects, we needed to take the value from the related picking. for example, for the `payment country code` linked to the package, we need to retrieve the value from the related picking or order. To avoid passing too much data to the request objects, it is convenient to be able to access to the order/picking related to the package directly from the package. Because these objects are not children of odoo.models.Model, I do not need to follow the convention for the names, however, calling the picking > picking_id in the DeliveryPackage suggests that the picking is actually a odoo.models.Model child, which should be the case if it exists. reference-PR= https://github.com/odoo/enterprise/pull/23124
This update adds data preparation scripts for appointment types and available time slots, helping teams test and optimize appointment scheduling at scale. It supports better performance validation for both standard appointments and website-based appointment booking, while reminder behavior remains handled separately by the calendar module.
Original PR description
For performance purposes, populate script for appointment types and slots. Alarms/reminders are covered in the calendar module. Task-2728093 See odoo/odoo#83265