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: Translations and UI
DearRémi,Sharing our experiences:
we have just done the translations for our ITISeasy.business V14 the fork from odoo 14 community that has some 170 extra modules from our side, for all the German terms (translated from en_US).
We wrote a module to find all the terms needed.
It were about 49000 terms to translate, consisting of single words as well as whole sentences. Picking the right term constantly is tricky.
First we have used a paid service the get the po-file pretranslated (poedit), but this is only beginning.
Auto translate is cumbersome, so we did manual retranslation with a team of 6 people, with great knowledge of ITISeasy.business, because the forms/messageboxes are not necessarily visible during translation. this would be really great if the po file could contain a link to the form that needs translation to get the "context"
In particular, we did quite some extensions to surveys, so you can store an duplicate sections and build a new survey more quickly with it. We also dealt with translations there, but mainly because of the wrong language preset.
Maybe this can help a little for the process you are going through. If you need anything, just drop me a mail
Best, Joe
joel@itis.us or jlorenz@itis.de
Von: "Rémi CAZENAVE - Le Filament" <remi@le-filament.com>
An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Gesendet: Dienstag, 7. September 2021 10:22:26
Betreff: Translations and UIDear all,
We are struggling with dealing with translations for one of our customers using mainly advanced surveys (with Odoo 12.0).
Basically, they design all their surveys in French + they use template surveys that they duplicate for new ones, changing titles and a few labels / questions inside.
Then they need to translate these surveys in English and German, since some of them are sent to non-French speaking companies.
Because Odoo considers that sources terms are en_US, we have everywhere names in source terms like "template (copy)", which is of course not the term they need to translate in English and German but the French terms are to be translated in these languages. Also names in survey tables are the original en_US ones (with (copy) inside) which means nothing to them...
I am not sure how to address this ? I have seen a number of issues on GitHub which are marked as normal behaviour and won't fix, but of course this does not help.
I have tried a few things, and my last idea is the following : force context to lang = en_US and do not translate in French (leave terms untranslated) so that it will use source terms for French. Then activate en_GB and de_DE for translating french source in these languages.
I have tried using context="{'lang': 'en_US'}" on translated fields in views but this does not seem to be taken into account, only context in action is but this use all fields in English then (meaning labels, group strings, etc.), which is not the intended purpose.
We will probably override write() actions to force lang in context.
I suppose many of you have already faced issues with translations, any idea, remark, link is welcome !
Best Regards,
--

Rémi CAZENAVE
------
SCOP LE FILAMENT_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Joerg Lorenz. - 12:25 - 7 Sep 2021 -
Re: A methodology / best practice / Odoo / Python question
Hi,you can also use functions to render QWeb templates, so you can declare the function in any Python file and add it to the values used to render the pages that will need your function.For instance, see how `format_date` is used in https://github.com/odoo/odoo/blob/070bec2f3a7a50c6fc8f104cf92a9416ebc001b8/addons/mail/models/mail_render_mixin.py#L244 for rendering e-mails.To add your function to the values of any website page you can override `_prepare_qcontext` (https://github.com/odoo/odoo/blob/3f96cff0aa5097a386c289cf9fd2aeb3048376ab/odoo/addons/base/models/ir_ui_view.py#L1720) or you can add it individually to the values of the page that need your function.On Mon, 6 Sept 2021 at 10:26, Radovan Skolnik <radovan@skolnik.info> wrote:Hello,
I am struggling with this for a while so I have decided to ask here. I am building a module that would be showing active filters/ordering as tags on e-commerce by parsing query part of the URL. Besides the standard ones (search, order) we are also using brands filter and also custom_info. Both of these can have multiple options checked. User has the option to remove them individually instead of searching for appropriate checkobxes on the page. Now my approach is basically iterate through key/value pairs and for each generate what looks like a tag visually with URL that has that key/value pair removed (so it in fact removes that part of filter). For that I have devised a code like this:
from odoo.http import request
from werkzeug import OrderedMultiDict
from werkzeug.urls import url_parse, url_encode
def _get_filtered_url(param, value):
filtered_args = OrderedMultiDict(filter(lambda arg: arg[0]!=param or arg[1]!=value, request.httprequest.args.items(multi=True)))
url = url_parse(request.httprequest.url)
return url.replace(query=url_encode(filtered_args)).to_url()
Now this code is obviously not a object/class method - it should be (in my opinion) a static method. Now the question is: static method of what? Because I need to be able to call it from XML template that renders part of WebsiteSale. I guess I could create a dummy (transient?) class and call it like request.env['my_transient_class']._get_filtered_url(param, value) but that somehow does not seem right to me. Or is it the right way? I am trying to write a clean concise code that is not hacky.
Any advice is welcome here. Thank you very much.
Best regards
Radovan Skolnik
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Simone Rubino - 10:31 - 7 Sep 2021 -
Translations and UI
Dear all,
We are struggling with dealing with translations for one of our customers using mainly advanced surveys (with Odoo 12.0).
Basically, they design all their surveys in French + they use template surveys that they duplicate for new ones, changing titles and a few labels / questions inside.
Then they need to translate these surveys in English and German, since some of them are sent to non-French speaking companies.
Because Odoo considers that sources terms are en_US, we have everywhere names in source terms like "template (copy)", which is of course not the term they need to translate in English and German but the French terms are to be translated in these languages. Also names in survey tables are the original en_US ones (with (copy) inside) which means nothing to them...
I am not sure how to address this ? I have seen a number of issues on GitHub which are marked as normal behaviour and won't fix, but of course this does not help.
I have tried a few things, and my last idea is the following : force context to lang = en_US and do not translate in French (leave terms untranslated) so that it will use source terms for French. Then activate en_GB and de_DE for translating french source in these languages.
I have tried using context="{'lang': 'en_US'}" on translated fields in views but this does not seem to be taken into account, only context in action is but this use all fields in English then (meaning labels, group strings, etc.), which is not the intended purpose.
We will probably override write() actions to force lang in context.
I suppose many of you have already faced issues with translations, any idea, remark, link is welcome !
Best Regards,
--

Rémi CAZENAVE
------
SCOP LE FILAMENT
by Rémi Cazenave - 10:21 - 7 Sep 2021 -
A methodology / best practice / Odoo / Python question
Hello,
I am struggling with this for a while so I have decided to ask here. I am building a module that would be showing active filters/ordering as tags on e-commerce by parsing query part of the URL. Besides the standard ones (search, order) we are also using brands filter and also custom_info. Both of these can have multiple options checked. User has the option to remove them individually instead of searching for appropriate checkobxes on the page. Now my approach is basically iterate through key/value pairs and for each generate what looks like a tag visually with URL that has that key/value pair removed (so it in fact removes that part of filter). For that I have devised a code like this:
from odoo.http import request
from werkzeug import OrderedMultiDict
from werkzeug.urls import url_parse, url_encode
def _get_filtered_url(param, value):
filtered_args = OrderedMultiDict(filter(lambda arg: arg[0]!=param or arg[1]!=value, request.httprequest.args.items(multi=True)))
url = url_parse(request.httprequest.url)
return url.replace(query=url_encode(filtered_args)).to_url()
Now this code is obviously not a object/class method - it should be (in my opinion) a static method. Now the question is: static method of what? Because I need to be able to call it from XML template that renders part of WebsiteSale. I guess I could create a dummy (transient?) class and call it like request.env['my_transient_class']._get_filtered_url(param, value) but that somehow does not seem right to me. Or is it the right way? I am trying to write a clean concise code that is not hacky.
Any advice is welcome here. Thank you very much.
Best regards
Radovan Skolnik
by Radovan Skolnik - 10:25 - 6 Sep 2021 -
Re: What do you want to learn about at OCA Days 2021?
Open Upgrade best practice for contributors in more detail would interest me.On Fri, Sep 3, 2021, 16:51 Pierre Verkest <pierreverkest84@gmail.com> wrote:Hi there,What could be interesting from my point of view, would be:- sharing on integration workflow, how do we manage module update (not migrating major version) to unfreeze version, test and deploy to production to avoid side effect according different instance diversities- get into short tracks that would present OCA modules from the functional point of view to get more informations on existing module (in any domain DDMRP, sales...)regardsLe jeu. 2 sept. 2021 à 10:47, Rebecca Gellatly <rebecca@o4sb.com> a écrit :HI everyone,I hope you are all well.
We are in full planning mode for the OCA Days (28th-29th Oct) and would love to hear from you.Are there talk topics, tutorials etc you would like to see presented at the OCA Days?Please give us an idea about what you want to know about.
Thanks so much,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Pierre_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kitti Upariphutthiphong - 09:31 - 6 Sep 2021 -
Re: What do you want to learn about at OCA Days 2021?
Hi there,What could be interesting from my point of view, would be:- sharing on integration workflow, how do we manage module update (not migrating major version) to unfreeze version, test and deploy to production to avoid side effect according different instance diversities- get into short tracks that would present OCA modules from the functional point of view to get more informations on existing module (in any domain DDMRP, sales...)regardsLe jeu. 2 sept. 2021 à 10:47, Rebecca Gellatly <rebecca@o4sb.com> a écrit :HI everyone,I hope you are all well.
We are in full planning mode for the OCA Days (28th-29th Oct) and would love to hear from you.Are there talk topics, tutorials etc you would like to see presented at the OCA Days?Please give us an idea about what you want to know about.
Thanks so much,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Pierre
by Pierre Verkest - 11:50 - 3 Sep 2021 -
Re: What do you want to learn about at OCA Days 2021?
Hello,
It would be nice to hear more about the OCA python packaging infrastructure:
- how and when are addons published on PyPI
- how to package you own addons
- example development workflows & deployment strategies using pip instead of a git based approach.
I don't think it has been covered in much details previously.
Thank you for the effort!
Kind Regards,
Kiril
On 2.9.21 10:46, Rebecca Gellatly wrote:
HI everyone,
I hope you are all well.
We are in full planning mode for the OCA Days (28th-29th Oct) and would love to hear from you.
Are there talk topics, tutorials etc you would like to see presented at the OCA Days?Please give us an idea about what you want to know about.
Thanks so much,Rebecca
--
Rebecca GellatlyGeneral SecretaryOdoo Community Association_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Lambda IS DOOEL - free/open-source information systems implementation & development Kiril Vangelovski - consultant/developer web: https://www.lambda-is.com tel: +38971753823
by Kiril Vangelovski - 12:31 - 2 Sep 2021 -
-
What do you want to learn about at OCA Days 2021?
HI everyone,I hope you are all well.
We are in full planning mode for the OCA Days (28th-29th Oct) and would love to hear from you.Are there talk topics, tutorials etc you would like to see presented at the OCA Days?Please give us an idea about what you want to know about.
Thanks so much,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 10:45 - 2 Sep 2021 -
[28984] Scaling and healing issues with Odoo.SH, any experiences / further documentation available
Dear community of Odooers, Odoo.SH plattform, based on a not precisely known method pauses cron jobs. Our analysis shows that the pause of a period T happens, if a job A produces a certain amount of errors Y within a certain period Z of time. Furthermore if the load exceeds some magic threshold entire systems seem to be shut down by the higher level VM environment causing the Odoo Server to restart. Especially for larger installations in productive usage this is inacceptable. So we are wondering if this or similar behaviour is specified and documented somewhere or others did make the same or similar experiences with Odoo.SH. This knowledge would be very valuable in either decide when to pull the plug on SH or at least how to monitor and prevent those situations from happening. Best Frederik P.S.: It is clear that for a cloud environment to operate properly such measures shall be taken but at least they must clearly be documented P.P.S: What i found was this https://www.odoo.com/documentation/master/administration/odoo_sh/advanced/frequent_technical_questions.html basically saying that and why they are doing it but not on the basis of which measures and that https://www.odoo.com/de_DE/forum/hilfe-1/odoo-sh-performance-sizing-142865 -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 03:36 - 1 Sep 2021 -
Re: Migration 12.0 -> 14.0
Oh, I don't pretend to make a such request 😅I thought that Github was able to give enough fine control to create a "Moderator" group across all OCA's modules projects to include users that would be able to edit issues or tag PRs with labels.I don't have any knowledge on Github bots, but would it be possible to have specific commands that would add/update the task list for Issues named like "Migration to version xxx" ?Analyse the current task list and update the check status based on the linked PR/ocabot migration-issueAdd a module to the task list:/ocabot migration-issue module_nameAdd/edit a module to/from the task list and link it with a PR:/ocabot migration-issue module_name #123Add/edit a module to/from the task list and add/edit a comment:/ocabot migration-issue module_name "Merged with another_module"/ocabot migration-issue module_name "Move to OCA/another_repo"--
Yann PAPOUIN, Ingénieur R&D | DECLe mar. 31 août 2021 à 15:37, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Well, for having such permission you need to be PSC of the area of the repository. You can propose yourself in this list if you think you have enough contributions for such place. More information at https://odoo-community.org/page/oca-project-steering-committee-guideRegards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yann Papouin - 02:40 - 1 Sep 2021 -
Re: Migration 12.0 -> 14.0
Well, for having such permission you need to be PSC of the area of the repository. You can propose yourself in this list if you think you have enough contributions for such place. More information at https://odoo-community.org/page/oca-project-steering-committee-guideRegards.
by Pedro M. Baeza - 03:35 - 31 Aug 2021 -
Re: Migration 12.0 -> 14.0
Thank you, that's good news.I've started an audit on our database to know current OCA module migration status before starting on it.This is really complicated (long task in fact) as for each module, you need to know the github repo and find the "Migration to version 1x.0" issue, and this one is not always updated with the latest comments.To help the community, is there a way to give me write access to the main topic to edit/update the task list ?--
Yann PAPOUIN, Ingénieur R&D | DECLe mar. 31 août 2021 à 10:31, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :Yes, that's possible while respecting commit history. If the 13.0 version ever needed, it can be backported from 14.0, or migrated from 12.0 again.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yann Papouin - 02:21 - 31 Aug 2021 -
Re: Migration 12.0 -> 14.0
Yes, that's possible while respecting commit history. If the 13.0 version ever needed, it can be backported from 14.0, or migrated from 12.0 again.Regards.
by Pedro M. Baeza - 10:30 - 31 Aug 2021 -
Migration 12.0 -> 14.0
Hello everyone,Is it allowed to create a PR for a module migration that bypasses 13.0 ?
Yann PAPOUIN
Ingénieur R&D | DEC
A ZAC du Monné 3 r Champ du Verger 72700 ALLONNES
T 02 43 21 65 50 ext 51 F 02 43 39 30 78 E ypa@decgroupe.com W www.decgroupe.com
by Yann Papouin - 10:26 - 31 Aug 2021 -
Re: Any module to make a user to have readonly access
Thanks Yoshi!Yes, I think we can use this. We will migrate to v13 / v14.KittiOn Thu, Aug 26, 2021 at 11:32 AM Yoshi Tashiro <tashiro@quartile.co> wrote:Hi Kitti,It may not be exactly what you are looking for in terms of achieving granular configuration, but here it is: https://github.com/OCA/server-tools/tree/12.0/base_model_restrict_update--Yoshi TashiroOn Thu, Aug 26, 2021 at 1:07 PM Kitti U. <kittiu@ecosoft.co.th> wrote:Hello,May I check if there is module or ideas that allow readonly access for any user (for auditor).- Without create group/role and access right model by model.
- All kind of buttons are disappear or not clickable.
Thank youKitti U._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kitti Upariphutthiphong - 07:40 - 26 Aug 2021 - Without create group/role and access right model by model.
-
Re: Any module to make a user to have readonly access
Hi Kitti,It may not be exactly what you are looking for in terms of achieving granular configuration, but here it is: https://github.com/OCA/server-tools/tree/12.0/base_model_restrict_update--Yoshi TashiroOn Thu, Aug 26, 2021 at 1:07 PM Kitti U. <kittiu@ecosoft.co.th> wrote:Hello,May I check if there is module or ideas that allow readonly access for any user (for auditor).- Without create group/role and access right model by model.
- All kind of buttons are disappear or not clickable.
Thank youKitti U._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Yoshi Tashiro. - 06:31 - 26 Aug 2021 - Without create group/role and access right model by model.
-
Any module to make a user to have readonly access
Hello,May I check if there is module or ideas that allow readonly access for any user (for auditor).- Without create group/role and access right model by model.
- All kind of buttons are disappear or not clickable.
Thank youKitti U.
by Kitti Upariphutthiphong - 06:05 - 26 Aug 2021 - Without create group/role and access right model by model.
-
Re: Travis logs full of "INFO openerp_test odoo.schema: Keep unexpected index"
Wow! fx from Sébastien Alix already coming in Odoo https://github.com/odoo/odoo/pull/75387On Mon, Aug 23, 2021 at 1:02 AM Raphaël Valyi <rvalyi@akretion.com> wrote:Hello contributors,So here is the temporary workaround I'm proposing in .travis.yml. At least it works for us in OCA/l10n-brazil: https://github.com/OCA/l10n-brazil/pull/1587/commits/d43e0eb3329a8116628259a1b6f5ec556e59efb5It basically just cd into the repo dir and reverts the commit.Example of build fixed https://app.travis-ci.com/github/OCA/l10n-brazil/builds/235949881I think I already used my quota :-p to bother Odoo SA about the pŕoblem created by this commit, so if somebody has got some good contact with the Odoo devs and can do the escalation dance thing to report them...Regards.On Sun, Aug 22, 2021 at 5:27 PM Raphaël Valyi <rvalyi@akretion.com> wrote:Hello Olaf,Okay so you found it: the "Keep unexpected index" comes from these recent Odoo changes indeed. In v12.0, the commit was made on June 4:https://github.com/odoo/odoo/commit/13f02a60c8706b808a57535ac9648a1b0c0741a9and the same day for OCB:I didn't have it in my source and it wasn't indexed in odoo/odoo that's why I didn't find it with grep.Now In Github it seems these commits are from June 4 and this is also why I didn't suspect this as we have builds much later than this date passing normally.But looking in this page it's actually clear that it was pushed by Robodoo 3 days ago:(in v13 and v14 here https://github.com/odoo/odoo/pull/66700 )So now I guess we should work on 2 fronts:- do the Odoo SA Github dance to tell Odoo SA their commit creates problems. But this could take months before being heard (I'm optimistic)...
- hack a palliative fix in Travis to avoid blocking the PR's in the meantime. I'll try that for now and update you.
On Sun, Aug 22, 2021 at 3:22 PM Olaf Wagner <wagner@elegosoft.com> wrote:On 22 Aug 2021, at 18:52, Raphaël Valyi wrote: > Hello contributors, > since 2 or 3 days ago max, on several OCA 12.0 builds one can see logs > full of "Keep unexpected index" log messages such as: > 2021-08-22 13:29:16,607 7203 INFO openerp_template odoo.schema: Keep > unexpected index ir_model_data_date_update_index on table > ir_model_data 1024 2021-08-22 13:29:16,607 7203 INFO > openerp_template odoo.schema: Keep unexpected index > ir_model_data_date_init_index on table ir_model_data 1025 2021-08-22 > 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep unexpected > index ir_model_data_create_uid_index on table ir_model_data 1026 > 2021-08-22 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep > unexpected index ir_model_data_create_date_index on table > ir_model_data 1027 2021-08-22 13:29:16,608 7203 INFO > openerp_template odoo.schema: Keep unexpected index > ir_model_data_write_uid_index on table ir_model_data 1028 2021-08-22 > 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep unexpected > index ir_model_data_write_date_index on table ir_model_data It’s from this change in the ORM: - https://github.com/odoo/odoo/commit/13f02a60c8706b808a57535ac9648a1b0c0741a9 - https://github.com/odoo/odoo/commit/b4647cbf1e483bcc42ff9962851f94c751e5eebb Must have been merged recently. I’ve encountered it in 13.0 and have disabled it locally as it was spamming our logs, too. Olaf -- Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany Geschäftsführer: Olaf Wagner | Sitz: Berlin Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ValyiFounder and consultant--Raphaël ValyiFounder and consultant_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 05:40 - 23 Aug 2021 -
Re: Travis logs full of "INFO openerp_test odoo.schema: Keep unexpected index"
Hello contributors,So here is the temporary workaround I'm proposing in .travis.yml. At least it works for us in OCA/l10n-brazil: https://github.com/OCA/l10n-brazil/pull/1587/commits/d43e0eb3329a8116628259a1b6f5ec556e59efb5It basically just cd into the repo dir and reverts the commit.Example of build fixed https://app.travis-ci.com/github/OCA/l10n-brazil/builds/235949881I think I already used my quota :-p to bother Odoo SA about the pŕoblem created by this commit, so if somebody has got some good contact with the Odoo devs and can do the escalation dance thing to report them...Regards.On Sun, Aug 22, 2021 at 5:27 PM Raphaël Valyi <rvalyi@akretion.com> wrote:Hello Olaf,Okay so you found it: the "Keep unexpected index" comes from these recent Odoo changes indeed. In v12.0, the commit was made on June 4:https://github.com/odoo/odoo/commit/13f02a60c8706b808a57535ac9648a1b0c0741a9and the same day for OCB:I didn't have it in my source and it wasn't indexed in odoo/odoo that's why I didn't find it with grep.Now In Github it seems these commits are from June 4 and this is also why I didn't suspect this as we have builds much later than this date passing normally.But looking in this page it's actually clear that it was pushed by Robodoo 3 days ago:(in v13 and v14 here https://github.com/odoo/odoo/pull/66700 )So now I guess we should work on 2 fronts:- do the Odoo SA Github dance to tell Odoo SA their commit creates problems. But this could take months before being heard (I'm optimistic)...
- hack a palliative fix in Travis to avoid blocking the PR's in the meantime. I'll try that for now and update you.
On Sun, Aug 22, 2021 at 3:22 PM Olaf Wagner <wagner@elegosoft.com> wrote:On 22 Aug 2021, at 18:52, Raphaël Valyi wrote: > Hello contributors, > since 2 or 3 days ago max, on several OCA 12.0 builds one can see logs > full of "Keep unexpected index" log messages such as: > 2021-08-22 13:29:16,607 7203 INFO openerp_template odoo.schema: Keep > unexpected index ir_model_data_date_update_index on table > ir_model_data 1024 2021-08-22 13:29:16,607 7203 INFO > openerp_template odoo.schema: Keep unexpected index > ir_model_data_date_init_index on table ir_model_data 1025 2021-08-22 > 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep unexpected > index ir_model_data_create_uid_index on table ir_model_data 1026 > 2021-08-22 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep > unexpected index ir_model_data_create_date_index on table > ir_model_data 1027 2021-08-22 13:29:16,608 7203 INFO > openerp_template odoo.schema: Keep unexpected index > ir_model_data_write_uid_index on table ir_model_data 1028 2021-08-22 > 13:29:16,608 7203 INFO openerp_template odoo.schema: Keep unexpected > index ir_model_data_write_date_index on table ir_model_data It’s from this change in the ORM: - https://github.com/odoo/odoo/commit/13f02a60c8706b808a57535ac9648a1b0c0741a9 - https://github.com/odoo/odoo/commit/b4647cbf1e483bcc42ff9962851f94c751e5eebb Must have been merged recently. I’ve encountered it in 13.0 and have disabled it locally as it was spamming our logs, too. Olaf -- Olaf Wagner -- elego Software Solutions GmbH -- http://www.elegosoft.com Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany Geschäftsführer: Olaf Wagner | Sitz: Berlin Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Raphaël ValyiFounder and consultant--Raphaël ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 06:01 - 23 Aug 2021