An error can occur before the (implicit) dialog service is up in this case, we trace the original error in the console as a fallback. runbot-error-110840 Forward-Port-Of: odoo/odoo#210132

An error can occur before the (implicit) dialog service is up in this
case, we trace the original error in the console as a fallback.

runbot-error-110840

Forward-Port-Of: odoo/odoo#210132

The failing step is creating a new website, which could take a long time. Increasing the timeout for the next step should prevent the error. runbot-error-104332 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#210121

The failing step is creating a new website, which could take a long
time. Increasing the timeout for the next step should prevent the error.

runbot-error-104332

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#210121

## Issue: When converting a lead to an opportunity, a wizard (`crm.lead2opportunity.partner`) is shown. This allows merging duplicated leads. However, if the most recently created lead is selected as the primary, the wizard record may be deleted unexpectedly. This usually goes unnoticed in the UI, as the wizard disappears after the operation. The issue becomes critical when overriding the conversion flow via a custom module or in future changes to the core logic. In those cases, t

## Issue:

When converting a lead to an opportunity, a wizard
(`crm.lead2opportunity.partner`) is shown. This allows merging
duplicated leads.

However, if the most recently created lead is selected as the primary,
the wizard record may be deleted unexpectedly. This usually goes
unnoticed in the UI, as the wizard disappears after the operation.

The issue becomes critical when overriding the conversion flow via a
custom module or in future changes to the core logic. In those cases,
the deletion of the wizard can lead to empty recordsets and errors.

#### Affected versions: 16.0 and later.

## Explanation

The `crm.lead2opportunity.partner` model has a `Many2one` field
`lead_id` that is being deleting on cascade which is the default
for m2o fields on transient models.

During lead conversion, action_apply() calls _action_merge() or
_action_convert(). In _action_merge(), non-primary leads are
unlinked. If the primary lead is the last created one, it differs
from the one referenced by the wizard. This causes lead_id to be
unset, triggering the cascade and deleting the wizard.

## Impact:

If a custom module overrides action_apply() or _action_merge() and
calls super() first, it may operate on an empty recordset, leading
to failures when trying to access data or call methods.

## To reproduce:

With debugger:

- Set a breakpoint on the unlink call inside _action_merge
- After unlink, calling self.exists() on the wizard will return an empty recordset

With a custom module:

- Override action_apply() or _action_merge()
- Call super() first
- Try to merge leads and select the most recent one as primary
- The wizard record will be deleted before your custom logic executes, and will raise a "Record does not exist or has been deleted."

OPW-4773172

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#209795

Description ----------- Installing the `helpdesk_timesheet` module on databases with millions of `account.analytic.lines` would reach the default memory limit of 2 GiB due to excessive ORM caching. The main memory consumption came from `_check_no_link_task_and_ticket` and `_compute_helpdesk_ticket_id` methods loading large amounts of records into the ORM cache. This commit adds manual column initialization and optimizes constraints to reduce ORM cache memory usage. Reference ------

Description
-----------
Installing the `helpdesk_timesheet` module on databases with millions of `account.analytic.lines` would reach the default memory limit of 2 GiB due to excessive ORM caching.

The main memory consumption came from `_check_no_link_task_and_ticket` and `_compute_helpdesk_ticket_id` methods loading large amounts of records into the ORM cache.


This commit adds manual column initialization and optimizes constraints to reduce ORM cache memory usage.

Reference
---------
opw-4743742

Forward-Port-Of: odoo/enterprise#85974

*l10n_es_real_estates,l10n_es_reports,l10n_es_reports_2024 Related to https://github.com/odoo/odoo/pull/210804 Forward-Port-Of: odoo/enterprise#85966

*l10n_es_real_estates,l10n_es_reports,l10n_es_reports_2024

Related to https://github.com/odoo/odoo/pull/210804

Forward-Port-Of: odoo/enterprise#85966

Sendcloud and ups_rest miss the override to allow sending the actual type of the carrier (in a recognizable way) to Amazon. opw-4771192 Forward-Port-Of: odoo/enterprise#84772

Sendcloud and ups_rest miss the override to allow sending the actual type of the carrier (in a recognizable way) to Amazon.

opw-4771192

Forward-Port-Of: odoo/enterprise#84772

This commit is a partial revert of e73c06b that fixes the following: 1. Outdated sections were removed from the report and kept in the model, in order to comply with stable policy. They were mistakenly removed from the compute, which didn't comply with stable policy. This commit brings them back, fixing outdated views. 2. Changes in the aforementioned commit included a misalignemnt between section Appendices C and D and their XML page names (which became D and E respectively). This commit

This commit is a partial revert of e73c06b that fixes the following:

1. Outdated sections were removed from the report and kept in the model, in order to comply with stable policy. They were mistakenly removed from the compute, which didn't comply with stable policy. This commit brings them back, fixing outdated views.

2. Changes in the aforementioned commit included a misalignemnt between section Appendices C and D and their XML page names (which became D and E respectively). This commit fixes their names.

task-4587067

Forward-Port-Of: odoo/enterprise#85382