Thursday, May 22, 2025
4 changes · saas-18.2
Resolved issues and error corrections
This fix prevents accounting test failures when localization demo data depends on other demo data that is not installed. The tests now only check localization demo data when the base accounting demo data was successfully loaded, improving reliability without changing business workflows.
Original PR description
l10n's contain demo data to be loaded, these are triggered from a function call inside the demo data file. account also has additional tests to verify the demo data loading, and reloading of demo data when the chart of accounts changes. but since the l10n demo data often relies on demo data from dependency modules, issue could arise when the dependent demo data is not available eg. `without-demo=True`. To circumvent this, these tests conditionally test the l10n demo data iff the account module has successfully installed demo data. Issue report on https://github.com/odoo/odoo/pull/197588#issuecomment-2667929919
This fixes an internal automated test that could fail unpredictably during nightly checks because it depended on the current time. By freezing time in the test, the team gets more stable quality checks and fewer false alarms during release validation.
Original PR description
Alays use a freeze_time when adding time-based tests. Runbot-223332
Users can now start configuring a server action without first selecting a model without triggering an error screen. The system checks that the required model information exists before using it, making setup smoother and preventing an avoidable crash.
Original PR description
Currently, an error produced on creating a new server action if the user selects a field in the **Action Details** without specifying a model. **Steps to Reproduce:** 1) Navigate to `Settings>Technical>Actions>Server Action`. 2) Click on `New Server Action`. 3) Select the field in Action Details without selecting the Model. 4) Observe the Error. **Error:** KeyError: False **Root Cause:** - The error occurs because the system attempts to access `self.model_id.model` at [1] without verifying it exists or not, which leads to a `KeyError`. [1]-https://github.com/odoo/odoo/blob/4fa26954bbb5f6a9c9679b7d44ec2261057da29e/odoo/addons/base/models/ir_actions.py#L820 **Solution:** - This commit prevents errors by adding checks to ensure model_id and model_id.model are present before accessing them. Sentry-6591474450
This fix prevents an error when processing Hong Kong payroll records for married employees who do not have a spouse name entered. It improves reliability by allowing optional spouse information to remain blank without interrupting payroll-related workflows.
Original PR description
When the status is married and no spouse name is provided, it raises a traceback. So we check that there is a spouse name before trying to upercase it, because the field is not required.