Wednesday, August 29, 2018
3 changes
Resolved issues and error corrections
This fix makes JavaScript errors easier to find and understand in automated build logs. It helps teams diagnose failed tests faster by showing important browser error details directly near the related failure instead of only in full logs.
Original PR description
Since chrome headless have been merged, js error messages are difficult to read: some information was missing or only displayed in full all log. All console.error() will now be displayed in build details, and will appear just before the python assertion. XMO's improvement will also be used on all log: Using module and classname of the class calling phantomJS. Also: some small improvements on error message to make them easier to read
This fixes an issue in the mail activity notification area so users see more accurate systray notifications. It also improves related test coverage to help prevent the problem from coming back.
Original PR description
Pad:https://pad.odoo.com/p/r.ca63eb1bd13b0c9a6f0d796636db1fa3 Task:https://www.odoo.com/web#id=1873614&action=333&active_id=1278&model=project.task&view_type=form&menu_id=4720 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
This fixes a date handling issue that could prevent Mexican electronic invoices from being validated. Businesses using Mexican localization should see smoother invoice and payment processing without this validation error.
Original PR description
Fix error when setting invoice_date on action_date_assign, and set time_invoice to avoid error with time() method on a string. To reproduce: - Create an invoice - Validate invoice - An error like this is displayed: `TypeError: 2018-08-06 12:38:46.742087-05:00 (field account.invoice.date_invoice) must be string or date, not datetime.` Also was fixed the use the fields like datetime and not how str in the test