Saturday, January 11, 2025
2 changes
Resolved issues and error corrections
This fixes how Odoo's web test system clears memory between test groups after a Chrome browser change made results inconsistent. It helps keep automated test runs stable and predictable, reducing false alarms in development workflows.
Original PR description
Since [1], we force the garbage collector to run between each hoot test suite. However, since chrome 124, this no longer seemed to produce the desirable effect. Indeed, memory graphs of the test suites were no longer predictable. The garbage collector seemed to work differently from a build to another, even with the same code. This is probably due to this change [2] in chrome, coming with version 124. Hopefully, the commit message gave us a hint on a way to fix our issue. [1] https://github.com/odoo/odoo/commit/a3ef39dae4a7cd6c96f14958744ac8d8bd2064c9 [2] https://chromium.googlesource.com/chromium/src/+/ae7269f134ede59c815b22c1fd042b26bab96b7a 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
The export option for updating existing data now correctly hides read-only fields. This prevents users from including values that cannot be re-imported or updated, reducing confusion and failed data update workflows.
Original PR description
Issue ----- Read-only fields appear in the export menu when the "I want to update data (import-compatible export)" checkbox is active. Cause ----- The `readonly` key is missing from the field dictionnary leading to all fields being considered as not read-only. https://github.com/odoo/odoo/blob/a546e2e5a87c311bef054ca4a6909e63d70c91fd/addons/web/controllers/export.py#L389-L390 Issue from 2b87effeb461acddf327884dd72c00ee22a4c9aa since only some attributes of the fields are fetched. opw-4446090