Tuesday, June 10, 2025
2 changes · saas-18.2
Resolved issues and error corrections
The automated checks for restaurant preset timing were adjusted to avoid a timing conflict that caused false failures in the validation system. This helps keep release testing stable without changing the point-of-sale experience for users.
Original PR description
Fix runbot error where opening quickly two times the `selectPresetTimingSlotHour` would ignore the second call since the method `openPresetTimin` is `asyncLocked`. Now, we only call it one time in the tours, which is sufficient for testing the presets. runbot error: 226439
This fixes an error that could occur when the Belgian CodaBox connection wizard was checked before company identification details were filled in. The change makes the setup process more reliable by safely handling missing VAT or registry information.
Original PR description
The test `test_computed_fields_without_dependencies` triggers all compute methods on new records (model.new()).
In `_compute_company_vat`, we had:
`re.sub(r'[^0-9]', '', wizard.company_id.vat or wizard.company_id.company_registry)`
When running on a new record, both `vat` and `company_registry` are `False`, so:
`re.sub(..., False)`
This causes `TypeError: expected string or bytes-like object, got 'bool'`.
We fix this by explicitly passing a string fallback.
[runbot-162081](https://runbot.odoo.com/odoo/error/162081)