Daily updates from Odoo
Wednesday, March 25, 2026
3 changes · saas-19.2
Enhancements to existing features
This update enhances the Project Side Panel by allowing more detailed budget information to be displayed. By enabling inheritance of a key method, the system now includes a broader range of budget items, providing project managers with a more complete financial overview. This improves decision-making related to project costs.
Original PR description
Enabling the inheritance of the method _get_budget_items to include more budget information, by adding a method for the budget items domain. Forward-Port-Of: odoo/enterprise#107466
This update adapts the French accounting import process to changes in how data is delivered from the system. Instead of downloading entire files, data is now streamed, improving efficiency and reducing download times. This ensures accurate and timely reporting for French-speaking customers.
Original PR description
This commit aims to adapt the usage of 'account.fr.fec' to the changes made in community. In particular `fec_data` field is not used any more. and we use `_get_fec_stream` to stream the content of the file. task-5404142 Forward-Port-Of: odoo/enterprise#111153 Forward-Port-Of: odoo/enterprise#102783
This update enhances debugging of Odoo's Chrome browser integration by capturing detailed logs when Chrome encounters issues, such as tab terminations. These logs provide more specific information than previous methods, aiding in identifying and resolving stability problems. The logging level can be adjusted for control and noise reduction.
Original PR description
Followup and partial revert of #232612: turns out chrome's stderr is worthless at best and confusing at worst (because it logs a bunch of dbus errors which don't actually matter), however chrome…
Followup and partial revert of #232612: turns out chrome's stderr is worthless at best and confusing at worst (because it logs a bunch of dbus errors which don't actually matter), however chrome turns out to have pretty extensive debug logging facilities which are somewhat valuable: https://www.chromium.org/for-testers/enable-logging/
For instance if the oomkiller decides to nuke a chrome tab (example selected for no reason whatsoever), the debug log will have an entry along the lines of
[...:WARNING::chrome/browser/ui/sad_tab.cc:256] Tab Killed: http://127.0.0.1:8069/
which is a much more helpful hint than just being told a test timed out (to say nothing of being told that chrome was not able to do dbus stuff when we never asked for that).
Because it can be useful for all sort of debugging, this log is saved not just when chrome fails to start, but also when a Chrome completes, successfully or unsucessfully (in the latter case it's logged as RUNBOT to be available from the runbot UI).
The chrome logging facilities are controlled by a new envvar `ODOO_BROWSER_LOG_VERBOSITY`, it can be set to `-1` to disable logging, or a strictly positive integer for ever increasing amounts of logging. At `1` chrome will log every network request it attempts which can be useful for debugging some races but is already extremely noisy.
Forward-Port-Of: odoo/odoo#255548
Forward-Port-Of: odoo/odoo#255054