Wednesday, July 24, 2024
7 changes · master
Resolved issues and error corrections
This fix renames an internal accounting field so it clearly represents multiple reversal entries rather than a single one. The change reduces confusion for teams and integrations working with refunds, reversals, expenses, sales, purchases, and local electronic invoicing flows, without changing business functionality.
Original PR description
…_move_ids *: hr_expense, l10n_es_edi_facturae, l10n_hu_edi,l10n_id_efaktur, l10n_it_edi_doi, purchase_stock, sale_mrp, sale_stock We introduced this field with a typo, now it causes misunderstanding as it is interpreted as a many2one and not a one2many. Related: https://github.com/odoo/odoo/commit/09a6a4da116059414baeb7e663d8a503c3ae082e task-no 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 fix reduces unnecessary memory messages when developers run browser tests manually, keeping the console easier to read. It also ensures automated test memory logs use more precise data, helping teams diagnose test behavior more reliably.
Original PR description
This commit does 2 things: - memory information logs (i.e. [MEMINFO]) were always logged, even when running JS unit tests in the browser manually. This was polluting the console with information that is available either way in the "memory" tab. Now these logs only appear when the garbage collector is exposed (i.e. when running unit tests through test_js.py); - since the "enable-precise-memory-info" flag wasn't applied, these memory logs were always displaying the same info accross multiple calls. This has been fixed by also checking that flag for all builds, along with the previously exposed "gc" flag. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an intermittent timing issue in the Documents deletion test that could cause automated checks to fail even when the product behaved correctly. The change helps keep quality checks stable and reduces false alarms during development.
Original PR description
Sometimes the following sequence happened after the steps in `restoreDocumentSteps` after those in `deleteWorkspaceSteps`: 1. We click on the trash section 2. Its header is re-rendered with the "active" class 3. We select the record 4. The kanban view is reloaded to actually show the trash now 5. We already selected the document, so we're at the step expecting to interact with the inspector. See runbot error 71617
The document deletion test now waits until the expected deleted item is actually loaded before continuing. This prevents false failures under slow network conditions and helps keep automated quality checks stable.
Original PR description
In this tour, there is a step that is supposed to check that the elements in trash are loaded.
.o_search_panel_field header.active:contains("Trash")
However, this is incorrect. If we put the network in slow 3G, we can see that the header has the active class while the trash elements are not yet loaded.
In this commit, we therefore ensure that chouchou is in the loaded elements before selecting it.This fixes an issue in Documents spreadsheets where renamed pivot measures were not properly supported. Business users can now rely on custom measure names appearing correctly, making spreadsheet reports clearer and easier to interpret.
This fixes a misleading internal field name used to track reversal entries across several accounting-related apps. The change reduces confusion for developers and maintainers without changing how business users work in Odoo.
Original PR description
…rsal_move_ids *: account_asset, account_reports, helpdesk_account, hr_payroll_expense, sale_subscription We introduced this field with a typo, now it causes misunderstanding as it is interpreted as a many2one and not a one2many. Related: https://github.com/odoo/odoo/commit/09a6a4da116059414baeb7e663d8a503c3ae082e task-no
Fixed an error that could occur when selecting or assigning tasks from the Project Gantt view. This keeps project planning workflows stable and avoids interruptions for users managing task schedules.
Original PR description
Steps to Reproduce: 1. Go to the Gantt view in tasks in the Project module. 2. Select a task. 3. Observe the traceback error. Cause: - The `Task.web_gantt_write()` method received an unexpected keyword in the data argument, causing a TypeError. Solution: - Updated the call of the `Task.web_gantt_write()` method to handle the data argument correctly. effected commit-https://github.com/odoo/enterprise/commit/214b52cb7d6d2087d2b18c2ff32a7b59b9b2e21b task-4057377