-
- Downloads
[FIX] pad: no deadlock on pad readonly modification
When the adapation without jQuery promise was done for 12.3 (in bfed5742) the hack for always saving a pad URL was added in the deferrence of the start method. This caused that in the following conditions: - pad URL is set - form is in edit mode - a change in the form change the readonly status of the pad => we would have a mutex lock (of the form change) waiting for the pad that is being rerendered to finish its start but that can only be done once the mutex is unlocked (because setValue of the pad is protected by the same mutex) => so we have deadlock and interface does not allow to save or do any other change. This happened for example if we had a project.project A without collaborative pad, project.project B with collaborative pad, and if we moved a task from project B to project A then back to project B. With this change, we get back to the behavior before bfed5742 of not waiting for the fake "setValue" in `start` of Pad. Without the change, added test fails with: Expected 1 assertions, but 0 were run because interface is deadlocked so write does not happen. opw-2150827 closes #41346 closes odoo/odoo#41363 X-original-commit: cc73abb218e17756b21824a192f4461eb8537c0e Signed-off-by:Nicolas Lempereur (nle) <nle@odoo.com>
Please register or sign in to comment