[13.0] update upstream 038354cb17d #3926
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If an user tries sending a invoice using an invoice address and a delivery address through snailmail, it would result in a traceback. This is due to the invoice address record not having a name. closes odoo/odoo#109681 Signed-off-by: Florian Daloze (fda) <[email protected]>
Chrome 111 enabled checking of websocket origin: if the WS connection sends an Origin head which is not whitelisted with the new `--remote-allow-origins` switch it is rejected. Turns out websocket-client (amongst others) *does* send an `Origin`, which trips the check, and means tours immediately break when trying to run them as Odoo's test harness is unable to connect to (and control) the devtools. Suppress sending `Origin` to fix the issue. Note: this also prevents using the remote developer tools by opening the devtools URL, user needs to go through chrome://inspect from the client and find / select the headless browser from there. Chrome 111 changeset: https://chromiumdash.appspot.com/commit/0154caeefc74530d5cb57ce71608beb1b77bca39 Chrome tracker issue: https://crbug.com/1422444 closes odoo/odoo#114930 Signed-off-by: Xavier Morel (xmo) <[email protected]>
…version change closes odoo/odoo#117886 X-original-commit: c38b5baaeac28a7952601878a5b5efadf7f52984 Signed-off-by: Christophe Simonis <[email protected]>
When we compare majorless scripts we must ignore the Odoo version.
Otherwise a module upgrade without major Odoo upgrade would fail to run
local scripts majorless scripts. That's what happens for example when
users click the upgrade button of a module.
Example: upgrade from `11.0.1.0` to `11.0.2.0`, with a local `2.0` folder
for upgrades.
```
11.0.1.0 < 11.0.2.0 < 11.0.2.0 -> False (check before this patch)
1.0 < 2.0 <= 2.0 -> True (check with this patch)
```
While still: upgrade from `11.0.2.0` to `12.0.2.0`
```
11.0.2.0 < 12.0.2.0 < 12.0.2.0 -> False (before this patch)
2.0 < 2.0 <= 2.0 -> False (with this patch)
```
closes odoo/odoo#119147
X-original-commit: 84ab74c62a19d08de8b6c7c4e3f3300d7e79bcf9
Signed-off-by: Christophe Simonis <[email protected]>
Before this commit: Files that should be ignored in the manifest but aren't (js library for example) it can happen that files have huge lines, the regex to substract the comments will overuse memory. For example, a file of 13M with a line of more that 8M characters, the memory consumptions peak at 1.7G The results might be different, but it's an acceptable compromise closes odoo/odoo#120111 X-original-commit: 0e56e4a7bd6de42d729441a53995ddd459d5e633 Signed-off-by: Thibault Francois <[email protected]>
mimic what is done for `odoo.addons` __path__. closes odoo/odoo#121045 Signed-off-by: Christophe Simonis <[email protected]>
Allow extending tests for any modules, regardless of existing ones in another entry of the `upgrade-path`. Bonus point: tests no longer need to be imported in the `__init__.py` file. closes odoo/odoo#121150 Signed-off-by: Christophe Simonis <[email protected]> Co-authored-by: Alvaro Fuentes <[email protected]>
…cy if none is defined in the journal closes odoo/odoo#121293 Signed-off-by: Quentin De Paoli <[email protected]>
Backport of d02851d59a1299aa0836381e58609b62e9fa3f98 --- On this situation: * P1 consumable product, kit, with components P2 and P3 in its BoM using 1 of each * P2 comsumable product, kit, with component P3 using 1 in the BoM * P3 storable product, 10 units in stock Before: The qyt_available for P1 is 10. That's incorrect: to assemble one P1 we need precisely two of P3s, one for P2 BoM then an extra for P1 BoM. After: The qyt_available for P1 is 5. closes odoo/odoo#123244 Signed-off-by: William Henrotin (whe) <[email protected]>
When there are too many (millions) of POS order lines associated to opened POS sessions we get too many taxes, most are duplicated. This causes a MemorryError. Example queries from a real DB: ``` > select count(distinct r.account_tax_id) from pos_order_line l join pos_order o on o.id = l.order_id join pos_session s on s.id = o.session_id join account_tax_pos_order_line_rel r on r.pos_order_ line_id = l.id where s.state != 'closed' +-------+ | count | |-------| | 24 | +-------+ > select count(r.account_tax_id) from pos_order_line l join pos_order o on o.id = l.order_id join pos_session s on s.id = o.session_id join account_tax_pos_order_line_rel r on r.pos_order_line_id = l.id where s.state != 'closed' +---------+ | count | |---------| | 2504539 | +---------+ ``` opw-3295467 closes odoo/odoo#124173 X-original-commit: 45d19b265033aa626e110e51d8b1d01408717a3e Signed-off-by: Christophe Simonis (chs) <[email protected]>
v13 backport of odoo/odoo#92117. opw-2951837 closes odoo/odoo#99292 Signed-off-by: Van Delft Aurélien (avd) <[email protected]>
…8354cb17d Solved conflicts on: - odoo/modules/module.py
|
looks broken, due to #3925 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solved minor conflict due to odoo/odoo@4ab8b28.