Saturday, December 6, 2025
2 changes · saas-18.3
Resolved issues and error corrections
This update resolves an issue where the server logging system was experiencing excessive queue buildup. The change reverts a recent update that increased the logging frequency, restoring a more stable and efficient logging process. This ensures data is recorded reliably without performance bottlenecks.
Original PR description
Based on this review of https://github.com/odoo/odoo/pull/238740 this pr reverts the flush interval to 0.5s introduced in https://github.com/odoo/odoo/pull/238648 to avoid queue saturation. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#238912
This update fixes an issue where time off calendar events weren't accurately reflecting the start and end times, particularly when time off was scheduled in a timezone different from UTC. The change ensures that calendar events correctly display the actual start and end times of time off requests, improving accuracy and usability.
Original PR description
**Steps to reproduce** - Have all timezones (browser, employee, working schedule...) aligned on an diffrent timezone than UTC (normal flow). - Take a time off for a half day, or in custom hours and validate it. Issue: the associated calendar event created doesn't match the time off start/end. **Cause** Commit 8c8c38b1d57971aa5ef220f720d4aeea86b6de98 converts the times from the time off (in UTC) to the leave's timezone, this is an issue because `start` and `stop` of `calendar.event` should be in UTC. **Change** The conversion makes sense for allday events, as the `start`/`stop` are not in UTC (see `_inverse_dates` in `calendar_event.py`, they represent a date used for the display of the event, but for non-allday events we have to make sure the `start`/`stop` are the actual times of the leave. opw-5225375 Forward-Port-Of: odoo/odoo#237818