Daily updates from Odoo
Wednesday, January 24, 2018
1 change
Resolved issues and error corrections
This fix prevents scheduling errors when global leave records do not have a timezone set. The system now safely uses UTC as a fallback, helping calendars and resource planning continue to work instead of failing with an exception.
Original PR description
When encoding global leaves, we put the timezone of this particular leave to False, which raises an exception when given directly to pytz. Simple solution is to pass 'UTC' in case we receive False. Next step is to really support timezones on global leaves. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr