Tuesday, April 9, 2024
7 changes · saas-17.2
Resolved issues and error corrections
This fix ensures candidate resume files can be uploaded even when the related recruitment conversation is still temporary and not yet saved. It prevents interruptions during applicant processing, helping recruiters keep their workflow smooth.
Original PR description
community: https://github.com/odoo/odoo/pull/160655
This fix prevents an error when users open a linked record from the Documents inspector after creating and validating a vendor bill. It ensures finance documents remain easy to navigate without interruptions.
Original PR description
Steps to reproduce =================== 1. Open Documents. 2. Go to finance and select a document. 3. Create a vendor bill using the action button. 4. Validate the vendor bill and go back to Documents. 5. Click on the link in the inspector. Error Occurred Technical ========== With commit https://github.com/odoo/odoo/commit/bc4ebf44e224a9e4dec0c924f835af52086ba4b6, in utils.js an object is returned for res_id in many2one_reference instead of value. After this PR ================== The linked record can be opened without error. Task-3777502
This fix centralizes a key background communication method used by Odoo's web services. It helps messaging, live chat, and related interface actions run more consistently, reducing the risk of errors in day-to-day communication workflows.
This fix ensures test communication channels are closed after each test run. It helps prevent memory buildup and keeps the test environment stable over repeated runs.
Original PR description
Before this PR, broadcast channels opened during a test would never be closed. This can lead to memory leak. Moreover, subscriptions to the message event are not cleaned as well so subscriptions would keep growing test after test. This PR ensures the channels are properly closed at the end of each test.
This fix corrects how message notification IDs are tracked in testing and mail-related services, preventing older notifications from overriding newer unread message counts. It helps ensure more reliable behavior and test coverage for messaging features.
Original PR description
Follow up of https://github.com/odoo/odoo/pull/160700 Follow up of HOOT commits In hoot mock server, values are stored "per model", which means the counter is stored in bus model and not in `this`. This issue made impossible to detect the last value (always undefined) and basically "diff" notifications were never discarded, which was not covered by any test, but it is better to fix it for future tests. `lastBusNotificationId` should be incremented before and not after assigning the id, as the initial counter should be 0, and the first notif should be 1. This is what was done on the legacy mock server. This becomes an issue in this commit as fixing the read of the last value (first point of commit) means "diff" notif were always discarded. Forgot to check the bus id with `needaction_inbox_counter` in `mail.message/mark_as_read`. Old `mail.message/mark_as_read` notifications could therefore alter the result of a more recent init value.
This fix makes Odoo's web test environment better match the real system when loading actions. It helps prevent misleading test results by supporting action lookup by both internal ID and XML identifier, including server actions that run immediately.
Original PR description
Before this commit, the mocked route was only able to load actions from their id. The actual route also allows to load them from their xml_id. Moreover, since a recent commit [1], server actions are directly run. [1] odoo/odoo@c3bfdfb0ae51e083e46b3d084d5f86e7083fcdd6 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 update fixes an internal test timing issue in the Mail app so automated checks run more reliably. It helps prevent false test failures and supports smoother delivery of future mail-related updates, with no direct change for end users.
Original PR description
HOOT currently does not isolate tests, and the promise used in `loadEmoji` is never discarded, leading to the RPC potentially being called after the end of the test. Waiting for the message to be present ensures the RPC is done within the correct test. runbot-60638 runbot-60673 runbot-61164 runbot-61261