Saturday, July 5, 2025
4 changes
Resolved issues and error corrections
A frequently unreliable automated test for editing chatter messages has been temporarily skipped to reduce false failures in Odoo's test infrastructure. This does not change customer-facing behavior and helps keep validation pipelines more dependable while the underlying timing issue is addressed later.
Original PR description
The test "Can edit message comment in chatter" fails often non-determinically on runbot. This happens because this test heavily uses the edit message feature, which has client-side code receiving…
The test "Can edit message comment in chatter" fails often non-determinically on runbot. This happens because this test heavily uses the edit message feature, which has client-side code receiving store data from both RPC returns and bus notifications. When CPU load is high which happens frequently on runbot, test shows race-condition where bus notifications are received much later than RPC return part and thus discuss state becomes wrong by having outdated data. This is an architectural issue that takes time to solve, so this test is skipped in the meantime. Note that while the problem occurs quite a lot on runbot in HOOT tests, in practice this happens quite rarely: bus notifications should be heavily throttled. Also HOOT test fails because of unfortunately case of receiving exactly outdated message body data before starting message edition. When message is being edited, any following store data with change of message body is ignored because the text in composer is intended to not change while editing the message. Kinda fixes runbot 227618 Forward-Port-Of: odoo/odoo#217501
The event attendee calendar view no longer crashes when opened. This fixes a missing search capability for event end dates, making the Events app more reliable for users managing registrations.
Original PR description
**Steps to Reproduce:** - Install the website and website_event module. - Navigate to Events -> Attendees -> Calendar View. Issue: - While accessing the calendar view, we are getting an error because that view needs the event_end_date field to be searchable. We have added search method for field [event_begin_date](https://github.com/odoo/odoo/pull/210532/files#diff-b8b0a21217ded7346150f1dd8353fbe2932e83f5e3d3755fd6e1c8281bb50c64R62) but missed it for event_end_date. opw-4892275 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#215809
Printing an Indian eWaybill no longer fails when the expiry date is missing from the response data. The report also now shows the correct document date, helping users rely on accurate invoice details.
Original PR description
Steps to reproduce: Traceback occurs when printing the eWaybill. When the eWaybill expiry date is not present in the JSON response, any usage of date.strftime(...) caused a traceback. This fix ensures the date is checked before formatting to prevent such errors. Possible issue after the post migration of the database to saas-18.1 opw-4919575 Forward-Port-Of: odoo/odoo#217535
The Work Entries Analysis report now only shows payroll data for the companies selected by the user. This prevents users in multi-company environments from seeing irrelevant company data and makes reporting more accurate.
Original PR description
BUG - In multi-companies env the report shows all the companies no matter what is selected in the company selection menu Expected behavior: - Only selected company data is presented in the view FIX - add a domain to the report action to show only allowed companies data Task: 4781100 Forward-Port-Of: odoo/enterprise#89451 Forward-Port-Of: odoo/enterprise#85690