Géry Debongnie
5ba1322f60
The `afternextrender` helper is meant to be used in some tests that want to do something after owl has completed all its work following a specific action. It is useful when the action may cause some additional renders, so waiting for one nextTick is not enough. Unfortunately, it has a bug: it waits for Owl scheduler to be empty. But in some cases, when a component is destroyed because of an error, the scheduler task list will not be cleared until the next render completes. It is implemented that way in Owl to reduce the amount of work it does. But this means that in some testing scenarios, the afterNextRender promise will simply not be resolved, since there is no upcoming render to clear the tasklist. With this commit, we just avoid the issue by ignoring the fibers coming from destroyed component. Note that I think that it is not a good semantic for tests, as it is a little bit too "black-boxy". Ideally, we should rather wait for something in the DOM. There is a waitUntil helper somewhere that may be useful for this situation closes odoo/odoo#115229 X-original-commit: ca8d1e7ea74120dd088c78bb4916aa994e852a0f Signed-off-by: Aaron Bohy (aab) <aab@odoo.com> Signed-off-by: Géry Debongnie <ged@odoo.com>
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
To learn the software, we recommend the Odoo eLearning, or Scale-up, the business game. Developers can start with the developer tutorials