Xavier Morel
5cfd32db9c
When revamping the message fetching from the headless browser, since stacktraces are available (by default) on console.error and console.warning events I assumed it could / would be useful to show them in the Python-level log. And they *were* quite useful during the original fixing stage. However they turn out not to be very useful day-to-day: * they add a lot of noise and lead to the error message itself being lost in a big block of red / logging.error * when a tour fails (which is the vast majority of the failures) the JS stacktrace always points to the same location in the tour manager (the one which goes "this step never succeeded") which is completely useless * aside from being bundled, normal JS code (where the stacktrace could be useful) doesn't generally use console.warn or console.error, it's going to straight blow up with an exception in which case we always get a stacktrace Leave the stacktrace formatting for console.trace as that's pretty much the only point of using this instead of console.log. closes odoo/odoo#44343 X-original-commit: 34500853f39c9557852cb83cbc274f59d803922f Signed-off-by: Xavier Morel (xmo) <xmo@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