- Mailing Lists
- Contributors
- Re: Technical help on odoo cache framework
Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
Re: Technical help on odoo cache framework
Indeed, self.invalidate_cache() is fixing the issue when added after super().
I tried self.invalidate_cache(['move_raw_ids']) to avoid the "RPG vs Bug" solution but the issue stay the same.
About @api.depends, I read that it was used to trigger computed fields update.
After some testing, I'm pretty sure that it is a framework issue because to reproduce it, you need this particular case:
- ProductA MTO -
Manufacture
(BoM A)
- ProductB
MTO - Manufacture (BoM B)
- ProductC MTO - Buy
- ProductD MTO - Buy
BoM A Content:
- ProductB
- ProductC
BoM B Content:
- ProductD
When creating a new ProductA production, my inherited _generate_move() is correctly called for
ProductB
production but it fails for ProductA. If BoM content is switched, then it works fine...
The second clue that make me think that it is framework issue is the fact that the CacheMiss exception should not be raised in the UI and that the server does not report any issue on INFO/DEBUG handlers like if the exception had leaked to the UI unintentionally.
by Yann Papouin - 05:16 - 24 Apr 2020
Reference
-
Technical help on odoo cache framework
Hi everyone,I'm working on extending the mrp module but I'm stuck on a technical issue that could come from a lack of knowledge of the 12.0 odoo framework since I'm coming from 6.1An Odoo server in raised on the UI with the message 'stock.move(311659,).product_type' when I create a new mrp.production record but no traceback is available neither in the UI or the server log/console.After some step-by-step debugging I finally found the culprit, an exception CacheMiss is raised when I try to access the `product_type` field of the mrp.production.move_raw_ids One2Many fields.Do you have some tips for me that would help me to understand what is failing in my code ?class MrpProduction(models.Model):
_inherit = 'mrp.production'
@api.multi
def _generate_moves(self):
super(MrpProduction, self)._generate_moves()
for production in self:
# Assign consumable immediatly
consu_move_ids = production.move_raw_ids.filtered(
lambda r: r.product_type == 'consu'
)
consu_move_ids._action_assign()Regards,Yann Papouin
by Yann Papouin - 01:16 - 24 Apr 2020