-
-
Notifications
You must be signed in to change notification settings - Fork 497
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[16.0][MIG] website_sale_order_type: Migration to version 16.0 #826
[16.0][MIG] website_sale_order_type: Migration to version 16.0 #826
Conversation
Without this patch, it's easy that the tour fails randomly due to a timeout when generating the sales order report. These assets can take a long time, increasing when more addons are installed. In an integrated database, this patch makes the test go from this log: 2020-11-06 10:34:53,941 34 INFO devel werkzeug: 127.0.0.1 - - [06/Nov/2020 10:34:53] "POST /payment/transfer/feedback HTTP/1.1" 302 - 730 4.368 11.800 To this one: 2020-11-06 10:32:55,517 34 INFO devel werkzeug: 127.0.0.1 - - [06/Nov/2020 10:32:55] "POST /payment/transfer/feedback HTTP/1.1" 302 - 479 2.906 5.771 That's about 50% the time. In the same patch, I remove the `self.env` patch that was only needed for Odoo v11 and lower.
With the old tour, timeout problems started to occur, even with 7830084 This partially reverts that, and instead uses a simpler tour to test the creation of the SO. TT26399
If we don't trigger the onchanges, we won't get some of the default values that the order type has defined TT30235
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: e-commerce-15.0/e-commerce-15.0-website_sale_order_type Translate-URL: https://translation.odoo-community.org/projects/e-commerce-15-0/e-commerce-15-0-website_sale_order_type/
Currently translated at 100.0% (1 of 1 strings) Translation: e-commerce-15.0/e-commerce-15.0-website_sale_order_type Translate-URL: https://translation.odoo-community.org/projects/e-commerce-15-0/e-commerce-15-0-website_sale_order_type/es/
This one shouldn't be needed if the field is computed writable (which I think it is), but if not, the patch should be to make it on the base module, like we have done with this one: OCA/sale-workflow@788e2bc |
Yes, this can be a good chance to fix that |
Fix made in OCA/sale-workflow#2639 |
ea2a78c
to
967c785
Compare
This migration PR has been reopened as the fix made in sale_order_type did not cover the e-commerce flow. Therefore this module is still needed. @pedrobaeza can you check it too? I have decided to extend the methods that set the values that are overwritten in the e-commerce flow instead of the method that prepares the dictionary and calls these methods so that in case they are called from anywhere else the intended effect of this module is still in effect. |
/ocabot migration website_sale_order_type |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK for overriding these methods instead.
967c785
to
4f8b857
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Just a minor comment:
This PR has the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_description
should be removed.
4f8b857
to
79fc3e8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ocabot merge nobump
On my way to merge this fine PR! |
Congratulations, your PR was merged at de8bc01. Thanks a lot for contributing to OCA. ❤️ |
cc @Tecnativa TT44380
@stefan-tecnativa @chienandalu please review :)