Thursday, September 1, 2016
3 changes
Enhancements to existing features
HTTP 404 errors are now recorded as errors instead of informational messages. This makes missing-page or missing-resource issues easier for teams to spot and investigate quickly.
Original PR description
Description of the issue/feature this PR addresses: We have HTTP-404 error in the log but is not easy to identify because is a logger.info Current behaviour before PR: If you have a HTTP 404 error in your instance you see a `INFO` logger. Desired behaviour after PR is merged: If you have a HTTP 404 error in your instance you see a `ERROR` logger.
Code cleanup and technical improvements
This change reorganizes how Odoo manages database registries by moving responsibilities into one central Registry component. It is mainly an internal cleanup that should make maintenance easier while preserving existing business behavior.
Original PR description
Move all functionalities of the class `RegistryManager` to the class `Registry`. The major difference in API is that the registry of a database is obtained by calling `Registry(name)`; the latter does not create a new registry instance if it already exists. The other difference is that some class methods have been converted to instance methods.
This update reorganizes how Odoo reads and routes incoming emails, moving shared email parsing logic into common tools. It simplifies maintenance and prepares the mail gateway for future improvements, with little direct impact on day-to-day users.
Original PR description
https://www.odoo.com/web?#id=19524&view_type=form&model=project.task&action=333&active_id=248&menu_id=4720