When the user connect with Stripe in the payment provider and an API request takes longer than 60 seconds then a ReadTimeout error will occur.

Line 1: https://github.com/odoo/odoo/blob/29a40a30f3bf7a4a3a205e54fb84e569691d961f/addons/payment_stripe/models/payment_provider.py#L413-L418

Traceback on sentry:
```
TimeoutError: The read operation timed out
  File "urllib3/connectionpool.py", line 445, in _make_request
    six.raise_from(e, None)
  File "<string>", line 3, in raise_from
    # Permission is hereby granted, free of charge, to any person obtaining a copy
  File "urllib3/connectionpool.py", line 440, in _make_request
    httplib_response = conn.getresponse()
  File "http/client.py", line 1375, in getresponse
    response.begin()
  File "http/client.py", line 318, in begin
    version, status, reason = self._read_status()
  File "http/client.py", line 279, in _read_status
    line = str(self.fp.readline(_MAXLINE + 1), "iso-8859-1")
  File "socket.py", line 705, in readinto
    return self._sock.recv_into(b)
  File "ssl.py", line 1274, in recv_into
    return self.read(nbytes, buffer)
  File "ssl.py", line 1130, in read
    return self._sslobj.read(len, buffer)
ReadTimeoutError: HTTPSConnectionPool(host='stripe.api.odoo.com', port=443): Read timed out. (read timeout=60)
  File "requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "urllib3/connectionpool.py", line 755, in urlopen
    retries = retries.increment(
  File "urllib3/util/retry.py", line 532, in increment
    raise six.reraise(type(error), error, _stacktrace)
  File "six.py", line 719, in reraise
    raise value
  File "urllib3/connectionpool.py", line 699, in urlopen
    httplib_response = self._make_request(
  File "urllib3/connectionpool.py", line 447, in _make_request
    self._raise_timeout(err=e, url=url, timeout_value=read_timeout)
  File "urllib3/connectionpool.py", line 336, in _raise_timeout
    raise ReadTimeoutError(
ReadTimeout: HTTPSConnectionPool(host='stripe.api.odoo.com', port=443): Read timed out. (read timeout=60)
  File "odoo/http.py", line 2134, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1710, in _serve_db
    return service_model.retrying(self._serve_ir_http, self.env)
  File "odoo/service/model.py", line 133, in retrying
    result = func()
  File "odoo/http.py", line 1737, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1938, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 191, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 717, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/web/controllers/dataset.py", line 34, in call_button
    action = self._call_kw(model, method, args, kwargs)
  File "addons/web/controllers/dataset.py", line 26, in _call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "odoo/api.py", line 461, in call_kw
    result = _call_kw_multi(method, model, args, kwargs)
  File "odoo/api.py", line 448, in _call_kw_multi
    result = method(recs, *args, **kwargs)
  File "addons/sale/wizard/payment_provider_onboarding_wizard.py", line 31, in add_payment_methods
    return super().add_payment_methods()
  File "addons/payment/wizards/payment_onboarding_wizard.py", line 141, in add_payment_methods
    return self._start_stripe_onboarding()
  File "addons/sale/wizard/payment_provider_onboarding_wizard.py", line 36, in _start_stripe_onboarding
    return self.env.company._run_payment_onboarding_step(menu_id)
  File "addons/payment/models/res_company.py", line 51, in _run_payment_onboarding_step
    return stripe_provider.action_stripe_connect_account(menu_id=menu_id)
  File "home/odoo/src/custom/trial/saas_payment_stripe/models/payment_provider.py", line 87, in action_stripe_connect_account
    return super().action_stripe_connect_account(menu_id)
  File "addons/payment_stripe/models/payment_provider.py", line 152, in action_stripe_connect_account
    connected_account = self._stripe_fetch_or_create_connected_account()
  File "home/odoo/src/custom/trial/saas_payment_stripe/models/payment_provider.py", line 184, in _stripe_fetch_or_create_connected_account
    connected_account = super()._stripe_fetch_or_create_connected_account()
  File "addons/payment_stripe/models/payment_provider.py", line 326, in _stripe_fetch_or_create_connected_account
    return self._stripe_make_proxy_request(
  File "addons/payment_stripe/models/payment_provider.py", line 414, in _stripe_make_proxy_request
    response = requests.post(url=url, json=proxy_payload, timeout=60)
  File "requests/api.py", line 119, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "requests/sessions.py", line 544, in request
    resp = self.send(prep, **send_kwargs)
  File "requests/sessions.py", line 657, in send
    r = adapter.send(request, **kwargs)
  File "requests/adapters.py", line 529, in send
    raise ReadTimeout(e, request=request)

```

To handle this situation, the code has been updated to ensure that if the system takes more than 60 seconds to connect with Stripe then raises a logger warning.

sentry-4506249274

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

Currently, an exception occurs when a payment session has expired at [1], To handle this issue, raise a validation error instead of raise an exception.

link [1]: https://github.com/odoo/odoo/blob/677f7d0c6085dba4ab9c27a53b4c3fd2d88b190e/addons/payment/controllers/post_processing.py#L48

Traceback On Sentry:

```
Exception: tx_not_found
  File "odoo/http.py", line 2248, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1823, in _serve_db
    return self._transactioning(_serve_ir_http, readonly=ro)
  File "odoo/http.py", line 1843, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 134, in retrying
    result = func()
  File "odoo/http.py", line 1821, in _serve_ir_http
    return self._serve_ir_http(rule, args)
  File "odoo/http.py", line 1828, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2053, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 220, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 756, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/payment/controllers/post_processing.py", line 48, in poll_status
    raise Exception('tx_not_found')

```

sentry-4992700034

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

Currently, raise an error message in the report editor when trying to edit any reports in the studio mode.

error message: too many values to unpack (expected 2))

When we modify a report, the system tries to make a copy of it. To make this copy, the system needs to provide certain details like the name, mode key etc . At that time system tries to assign multiple values instead of two at this point [1] because the 'key' passed to do a copy of the report is [2] split by '.' as we see in [1] which leads to multiple values instead of two.

link [1]:  https://github.com/odoo/odoo/blob/1648ee1abff1ae12b3933baa85a2e048fa2eb557/odoo/addons/base/models/ir_ui_view.py#L102

link [2]:
https://github.com/odoo/enterprise/blob/34a042bb196273c34cd163f4c43bbd858664b7dc/web_studio/controllers/report.py#L337

To resolve the issue, Add limiting into split, To ensure that there are only two elements in the resulting list, which can unpacked into two (first is module, second is view_id) variables to prevent error.

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

Currently, the  error is generated when the client is trying to modify the view of an existing report through Web Studio.

Steps to reproduce:

- Install the 'web_studio' module and any other module that has report options available for example here we are using the 'account' module.
- Open 'Studio' in Invoicing and  (Turn on the debugger mode)
- Then go to 'Reports' and open any existing report.
- Click on 'More' option and then click on the '</>Qweb Views' button.
- Open the view and remove everything except the first and the last line, Save it now and go back to the report you modified the error will be generated.

```IndexError: list index out of range```

To resolve the issue, we will add a try-except block at [1] to handle errors. This will ensure that if an error occurs when accessing an edited report, it will raise a user error message and this error message will be seen in the report editor.

link [1]: https://github.com/odoo/enterprise/blob/6c538b5ba63be936120f38c90445dfbb2e65a625/web_studio/controllers/report.py#L583-L584

sentry-4650493111

Currently, The  error is occurs whenever user open a 'task' in portal view.

Steps to reproduce

- Install an 'industry_fsm' module.
- Open a portal view.
- Click on 'Tasks' and open an any record form it.

Traceback on sentry:

```
AttributeError: 'project.task' object has no attribute 'display_sign_report_primary'
  File "<2406>", line 1650, in template_2406
  File "<2406>", line 1632, in template_2406_content
  File "<2406>", line 555, in template_2406_t_call_0
  File "<2406>", line 473, in template_2406_t_call_3
  File "<2406>", line 73, in template_2406_t_set_12
QWebException: Error while render the template
AttributeError: 'project.task' object has no attribute 'display_sign_report_primary'
Template: ir.ui.view(2406,)
Path: /t/t/body/div[1]/div/t/t[2]/div/div[2]
Node: <div t-if="task.is_fsm and (task.display_sign_report_primary or task.display_sign_report_secondary)" class="d-grid flex-grow-1 align-items-center mb-2"/>
  File "odoo/http.py", line 2157, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1732, in _serve_db
    return service_model.retrying(self._serve_ir_http, self.env)
  File "odoo/service/model.py", line 133, in retrying
    result = func()
  File "odoo/http.py", line 1759, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 1873, in dispatch
    return self.request.registry['ir.http']._dispatch(endpoint)
  File "addons/website/models/ir_http.py", line 235, in _dispatch
    response = super()._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 209, in _dispatch
    result.flatten()
  File "odoo/http.py", line 1248, in flatten
    self.response.append(self.render())
  File "odoo/http.py", line 1240, in render
    return request.env["ir.ui.view"]._render_template(self.template, self.qcontext)
  File "addons/website/models/ir_ui_view.py", line 443, in _render_template
    return super()._render_template(template, values=values)
  File "odoo/addons/base/models/ir_ui_view.py", line 2044, in _render_template
    return self.env['ir.qweb']._render(template, values)
  File "odoo/tools/profiler.py", line 292, in _tracked_method_render
    return method_render(self, template, values, **options)
  File "odoo/addons/base/models/ir_qweb.py", line 593, in _render
    result = ''.join(rendering)
  File "<2406>", line 1656, in template_2406
```

When the user open a 'task' in portal view. There's an issue where the system attempts to access an attribute 'display_sign_report_primary'  from 'project.task' object [1] and the 'project.task' object has no attribute 'display_sign_report_primary'  at that specific point.

Line[1]:https://github.com/odoo/enterprise/blob/ce9122ab0fa8c393e4c37280fcef52377d6fb16f/industry_fsm/views/project_portal_templates.xml#L39

This commit solves this issue by accessing an attribute 'display_sign_report_primary' in the 'industry_fsm_report' module instead of 'industry_fsm' module. This adjustment is necessary as the 'display_sign_report_primary' attribute is not present in the 'industry_fsm'
 module.

sentry-4673429933

Currently, An error is generated when trying to open the 'Profit and Loss' report.

Steps to reproduce:

- Install an 'account_reports' module.
- Navigate to Accounting / Configuration / Management / Accounting Reports, Open 'Profit and Loss', Click on the 'Column' page, and change the value of 'Figure Type' to 'Datetime'
- Open reports Accounting / Reporting / Statement Reports / Profit and Loss.

Stack Trace:

```
AssertionError: null
  File "odoo/http.py", line 2248, in __call__
    response = request._serve_db()
  File "odoo/http.py", line 1823, in _serve_db
    return self._transactioning(_serve_ir_http, readonly=ro)
  File "odoo/http.py", line 1843, in _transactioning
    return service_model.retrying(func, env=self.env)
  File "odoo/service/model.py", line 134, in retrying
    result = func()
  File "odoo/http.py", line 1821, in _serve_ir_http
    return self._serve_ir_http(rule, args)
  File "odoo/http.py", line 1828, in _serve_ir_http
    response = self.dispatcher.dispatch(rule.endpoint, args)
  File "odoo/http.py", line 2053, in dispatch
    result = self.request.registry['ir.http']._dispatch(endpoint)
  File "odoo/addons/base/models/ir_http.py", line 220, in _dispatch
    result = endpoint(**request.params)
  File "odoo/http.py", line 756, in route_wrapper
    result = endpoint(self, *args, **params_ok)
  File "addons/web/controllers/dataset.py", line 38, in call_kw
    return self._call_kw(model, method, args, kwargs)
  File "addons/web/controllers/dataset.py", line 34, in _call_kw
    return call_kw(request.env[model], method, args, kwargs)
  File "odoo/api.py", line 458, in call_kw
    result = getattr(recs, name)(*args, **kwargs)
  File "home/odoo/src/enterprise/saas-17.2/account_reports/models/account_report.py", line 4441, in get_report_information
    'lines': self._get_lines(options, all_column_groups_expression_totals=all_column_groups_expression_totals, warnings=warnings),
  File "home/odoo/src/enterprise/saas-17.2/account_reports/models/account_report.py", line 2141, in _get_lines
    line_dict = self._get_static_line_dict(options, line, all_column_groups_expression_totals, parent_id=parent_generic_id)
  File "home/odoo/src/enterprise/saas-17.2/account_reports/models/account_report.py", line 2356, in _get_static_line_dict
    {'formula': expression.formula, 'subformula': expression.subformula, 'value': self.format_value(options, column_group_totals[expression]['value'], figure_type)}
  File "home/odoo/src/enterprise/saas-17.2/account_reports/models/account_report.py", line 4834, in format_value
    return self._format_value(options=options, value=value, figure_type=figure_type, format_params=format_params)
  File "home/odoo/src/enterprise/saas-17.2/account_reports/models/account_report.py", line 4870, in _format_value
    return format_date(self.env, value)
  File "odoo/tools/misc.py", line 1327, in format_date
    return babel.dates.format_date(value, format=date_format, locale=locale)
  File "babel/dates.py", line 700, in format_date
    return pattern.apply(date, locale)
  File "babel/dates.py", line 1232, in apply
    return self % DateTimeFormat(datetime, locale)
  File "babel/dates.py", line 1238, in __init__
    assert isinstance(value, (date, datetime, time))

```

The issue occurs when the system tries to format a value into a date at [1] that is not a string.

link [1]: https://github.com/odoo/enterprise/blob/d31f359e543a9413623d4a15aebba54e8d76d023/account_reports/models/account_report.py#L4797

To resolve this issue, Add a try-except block to handle errors that occur during date formatting

Sentry-5646185230

This PR is a cherry-pick of: https://github.com/odoo/odoo/pull/236323

When a pre-filter condition of an automation flushes fields, we must ensure that their recomputation is still scheduled afterwards For example, if a rule pre-filters on field B (which depends on A), computing A should not clear the compute flag of B

### Issue:
In some automation rules, computed fields must be processed in a specific order (e.g., `effective_hours` -> `remaining_hours`)
However, if `remaining_hours` is referenced in the automation `Before Update Domain`, its compute flag may be incorrectly cleared, preventing the proper recomputation chain

This results in inconsistent behavior, such as delays in activities being created when timesheets exceed allocated time

### Cause:
The automation engine flushes fields referenced in the `Before Update Domain`, but does not restore their compute flags afterward Thus dependent fields are not recomputed as expected

### Steps to reproduce:
1. Enable Debug Mode
2. Create an Automation Rule
-- Name: Time Exceeded
-- Model: Task
-- Trigger: On Save
-- Before Update Domain: [("remaining_hours", ">=", 0)]
-- Apply on: [("remaining_hours", "<", 0)]
4. Create a Project with Timesheets
5. Create a Task inside the Project
6. Set Allocated Time to 10h
7. Use the Start button to record 11h (No activity appears in chatter)
8. Do the same again (Activity appears only after the second exceed) Before the fix, there is always a delay because the recomputation chain is broken

### Tickets:
18.0: opw-4409744
17.0: opw-5237430

**Steps to reproduce:**
* Install the **Repair** module with demo data.
* From Setting -> enable 'Discounts' and 'Pricelists'
* From the home screen, search for Pricelist and open it.
* Open the default USD pricelist and go to Configuration →
`Show public price & discount to the customer`
* Open the *Repair* app.
* Create a **Repair Order with parts**.
* Click **Create Quotation** button from the repair order.
* In the quotation,  order line and set a **discount**.
* Return to the repair order using the **Repairs** smart button.
* Confirm the repair order, then **Start repair** and **End repair**  order.

**Observed behavior:**
* The discount added on the quotation line disappears from the linked sale order line.

**Cause:**
* The `discount` field on `sale.order.line` is computed by `_compute_discount`,
  which `depends` on `product_id`, `product_uom`, and `product_uom_qty`.
  When `product_uom_qty` is written during `action_repair_done`, the
  compute method is triggered and the `discount` is recalculated.
https://github.com/odoo/odoo/blob/49169c4c4fec57d78cd82c4c9366de9d69540e6a/addons/repair/models/repair.py#L457

**Fix:**
* Remove the for loop that calls `write()` on the sale order lines, as it
  is functionally incorrect and causes the discount to be reset.

---
opw-5352567

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