The recurring donation product now has a placeholder image, making it appear more polished and recognizable in the online store. This improves the presentation of donation options for website visitors without changing how donations work.

Added placeholder image for the recurring donation product.

task-6361612

The Timesheet Timeline view now shows assistant suggestions in true chronological order instead of sorting them by title. It also displays each suggestion's start time, making it easier for users to review and enter timesheets accurately.

Forward-Port-Of: odoo/enterprise#125574
Forward-Port-Of: odoo/enterprise#122862

Payroll batch processing has been optimized by removing unnecessary work entry generation and reducing repeated processing during payslip calculations. This should make large payroll runs noticeably faster, especially when computing many payslips at once.

Backport of https://github.com/odoo/enterprise/pull/124776 without the populate blueprint.

Forward-Port-Of: odoo/enterprise#126561
Forward-Port-Of: odoo/enterprise#125288

Added placeholder image for the donation product. Task-6361612 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Added placeholder image for the donation product. 

Task-6361612



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

Forward-Port-Of: odoo/odoo#278655

Forward-Port-Of: odoo/odoo#278655

We update the IoT Box version, so that it follow the new saas version (19.4). Forward-Port-Of: odoo/odoo#278588

We update the IoT Box version, so that it
follow the new saas version (19.4).

Forward-Port-Of: odoo/odoo#278588

Pycups has an issue where it can raise an error (1280) meanwhile the status is a success. We don't want to see a traceback in such case, so we skip logging in this case.

Pycups has an issue where it can raise an error (1280) meanwhile the status is a success.
We don't want to see a traceback in such case, so
we skip logging in this case.

Before this commit, expect.waitForSteps and expect.waitForErrors gave 2 seconds, less than the 3 seconds of the DOM waits sitting next to them, on the same page and the same RPCs. Over 340 call sites in addons tests reach waitForSteps and not one of them passes an explicit timeout, so 2 seconds is what every step wait gets. The problem is that the RPC chain a step wait sits on takes longer than that on a loaded machine. Measured from openDiscuss resolving to the message being in the DOM: -

Before this commit, expect.waitForSteps and expect.waitForErrors gave 2 seconds, less than the 3 seconds of the DOM waits sitting next to them, on the same page and the same RPCs. Over 340 call sites in addons tests reach waitForSteps and not one of them passes an explicit timeout, so 2 seconds is what every step wait gets.

The problem is that the RPC chain a step wait sits on takes longer than that on a loaded machine. Measured from openDiscuss resolving to the message being in the DOM:

- 250 to 460ms on an idle machine;
- 867 to 5258ms over 10 runs with the CPU throttled 4x, which is what a busy runbot looks like, 3 of the 10 over 2 seconds;
- 1474 to 6912ms with the CPU throttled 6x, 5 of 6 over 3 seconds.

Note that a longer timeout costs nothing on a green build: the timer is cleared as soon as the steps are in, so it only delays the report of a test that was going to fail anyway.

This commit raises both to 10 seconds, the delay a tour step already gets in macro.js. test_js.py runs the presets with timeout=15000, so hoot fails the test itself at 15 seconds and 10 leaves room for the rest of the test.

Companion of https://github.com/odoo/odoo/pull/279983 to fix https://runbot.odoo.com/odoo/error/944188 kind of issues.

Forward-Port-Of: odoo/odoo#279984