Saturday, June 22, 2024
6 changes · saas-17.2
Resolved issues and error corrections
The spreadsheet component was updated to the latest available version for this Odoo branch. This brings a small reliability fix for editing ranges in spreadsheets and includes documentation improvements, helping users have a smoother spreadsheet experience.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/1aaacc403 [REL] 17.2.12 Task: 0 https://github.com/odoo/o-spreadsheet/commit/3fdac0659 [IMP] documentation: improve commands documentation Task: 3989757 https://github.com/odoo/o-spreadsheet/commit/47dd5c619 [FIX] ComposerStore: missing previous range Task: 3972392 Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Mehdi Rachico (mera) <mera@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
Miscellaneous changes
Before this commit, `sale.order.line._compute_qty_at_date` method would compute only some `forecast_expected_date` at a time per loop. After this commit, `forecast_expected_date` is computed for all relevant moves in a single call. Given that `forecast_expected_date` has potential to be a slow computing field, we should minimize the number of times it is called. Log line stats for loading sale order S05312 | | # queries | SQL time | Odo
Original PR description
Before this commit, `sale.order.line._compute_qty_at_date` method would compute only some `forecast_expected_date` at a time per loop. After this commit, `forecast_expected_date` is computed for all…
Before this commit, `sale.order.line._compute_qty_at_date` method would compute only some `forecast_expected_date` at a time per loop. After this commit, `forecast_expected_date` is computed for all relevant moves in a single call. Given that `forecast_expected_date` has potential to be a slow computing field, we should minimize the number of times it is called. Log line stats for loading sale order S05312 | | # queries | SQL time | Odoo time | |------------------------------------------|---------------|---------------|-------------------------------| | before-commit | 31270 | 5.577 s | 187.606 s (timeout) | | after-commit | 31114 | 4.078 s | 10.663 s | | after-commit + PR #166784 | 233 | 0.430 s | 5.905 s | The PR #166784 stats are included just to show that there is not much more to be done in this PR to improve the query count, but that is addressed in the other PR. (Note that the customer's database is 17.0, not 15.0 - but I figured this could be made in 15.0 and fw-ported.) opw-3920584 Forward-Port-Of: odoo/odoo#169213 Forward-Port-Of: odoo/odoo#167085
Steps to reproduce in 17.0: There's no way to reproduce the issue in 17.0 because the faulty getter in only called on positions in the active sheet (pivot autofill, global filter auto-matching) Steps to reproduce in saas-17.1: - insert a pivot in a blank spreadsheet - delete all pivot formulas - insert a new sheet - in the new sheet: - in A1: type "1" - in A2: =ODOO.PIVOT(A1) - activate the first sheet again - Open the Data menu => the pivot 1 is marked as being unused, even th
Original PR description
Steps to reproduce in 17.0: There's no way to reproduce the issue in 17.0 because the faulty getter in only called on positions in the active sheet (pivot autofill, global filter auto-matching) Steps to reproduce in saas-17.1: - insert a pivot in a blank spreadsheet - delete all pivot formulas - insert a new sheet - in the new sheet: - in A1: type "1" - in A2: =ODOO.PIVOT(A1) - activate the first sheet again - Open the Data menu => the pivot 1 is marked as being unused, even though it's used in the second sheet Task: 3859472 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 Forward-Port-Of: odoo/odoo#168164 Forward-Port-Of: odoo/odoo#161108
opw-3950052 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 Forward-Port-Of: odoo/odoo#170114
Original PR description
opw-3950052 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 Forward-Port-Of: odoo/odoo#170114
Steps to reproduce: - Create a serial number tracked product. - Activate "Packages" setting from the "Inventory" app configuration. - Create a receipt order with a stock move of that product. - Mark it as to-do and generate serial numbers. - Click on "Detailed Operations" smart button. - Select some of the move lines and click on "Put in Pack". Expected behavior: - Only the selected move lines are put in a package. Current behavior: - All of the move lines are put in a package.
Original PR description
Steps to reproduce: - Create a serial number tracked product. - Activate "Packages" setting from the "Inventory" app configuration. - Create a receipt order with a stock move of that product. - Mark it as to-do and generate serial numbers. - Click on "Detailed Operations" smart button. - Select some of the move lines and click on "Put in Pack". Expected behavior: - Only the selected move lines are put in a package. Current behavior: - All of the move lines are put in a package. Task-3857396 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#168668
Adapt [werkzeug version for Ubuntu Noble](https://packages.ubuntu.com/noble/python3-werkzeug) mainly to avoid deprecation warnings in python 3.12. While at it, adapt for Bookworm as it provides [python 3.11](https://packages.debian.org/bookworm/python3). Forward-Port-Of: odoo/odoo#170311
Original PR description
Adapt [werkzeug version for Ubuntu Noble](https://packages.ubuntu.com/noble/python3-werkzeug) mainly to avoid deprecation warnings in python 3.12. While at it, adapt for Bookworm as it provides [python 3.11](https://packages.debian.org/bookworm/python3). Forward-Port-Of: odoo/odoo#170311