Monday, December 9, 2024
3 changes · master
Resolved issues and error corrections
Fixes an issue in Discuss where clicking “mark as read” did not always remove the new message banner, even when messages were already up to date on the server. This helps users keep a clearer view of unread activity and reduces confusion in chat channels.
Original PR description
A new message banner is displayed on discuss channels to help user keep track of their messages. Clicking on the "mark as read" button sometimes does not remove the banner. This happens since [1] because the value is kept locally and not updated anymore when clicking on the "mark as read" button. This PR fixes this issue. At the same time, this PR restores the `isDisplayedOnUpdate` patch that was incorrectly put on the thread component patch instead of the model. [1]: https://github.com/odoo/odoo/pull/188127
This fixes misleading negative timing values that could appear in HTTP test logs when test time is frozen. It improves the reliability of internal diagnostics without changing business workflows or user-facing behavior.
Original PR description
During HTTP case, if freeze gun is used, the remaing time (last number of the log line of the HTTP request) is negative (= -query_time). It is the case because we used time.time() which is patched by freezegun. To avoid this no-sense number, used the same trick than in `Cursor.execute`.
This fix ensures Knowledge article property settings are updated before their related values. It helps prevent inconsistent or failed updates when users change structured information in Knowledge articles.
Original PR description
For property fields, we should always update its definition field before updating its value. https://github.com/odoo/odoo/pull/182599