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
-
[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 -
Re: Travis logs full of "INFO openerp_test odoo.schema: Keep unexpected index"
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
by "Raphaël Valyi" <rvalyi@akretion.com> - 10:31 - 22 Aug 2021 -
Re: Travis logs full of "INFO openerp_test odoo.schema: Keep unexpected index"
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
by Olaf Wagner - 08:20 - 22 Aug 2021 -
Travis logs full of "INFO openerp_test odoo.schema: Keep unexpected index"
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_data10242021-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_data10252021-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_data10262021-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_data10272021-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_data10282021-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--some examples among many:A) OCA/product-attribute (3 days ago): https://app.travis-ci.com/github/OCA/product-attribute/jobs/532742269The strange logs are there but the build is still successful.B) OCA/l10n-brazil (a few hours ago): https://app.travis-ci.com/github/OCA/l10n-brazil/jobs/533085576The problem is that these "unexepected index" messages make the logs so verbose that the test job is killed because we are exhausting the log length quota in repos with lots of tests like OCA/l10n-brazil:"The job exceeded the maximum log length, and has been terminated."I can see no recent change in the Odoo 12.0 branch nor OCA/maintainer-quality-tools that could explain such changes. Seems there is no psycopg update either.Any idea how to fix this? This is blocking lot's of PR in repos such as OCA/l10n-brazil but I'm sure other repos will soon be blocked too.Best regards.Raphaël ValyiFounder and consultant
by "Raphaël Valyi" <rvalyi@akretion.com> - 06:50 - 22 Aug 2021 -
Re: /ocabot rebase and improved addons table
Thanks!On Fri, 13 Aug 2021 at 10:57, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Hi folks!I just deployed a new version of our GitHub bot with the following new features:A new /ocabot rebase command (contributed by Miquel Raïch).An update to the README.md addons table generator to show the addons maintainers (contributed by Sylvain Le Gal).Have a nice day,-sbi--_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Lorenzo Battistini
https://github.com/eLBati
by Lorenzo Battistini. - 05:35 - 19 Aug 2021 -
Re: Employee contract builder in Odoo
Yes agreement_legal should do the work. We use this all the time.On Wed, Aug 18, 2021, 23:57 Daniel Reis <dreis@opensourceintegrators.com> wrote:Yes, the oca/contract "agreement" module might do what you want.
Have a look at https://github.com/OCA/contract/tree/12.0/agreement_legal
Thanks
Daniel
On 18/08/21 17:37, Bruno Joliveau wrote:
Hi Tom,
I don't remember ever having seen such a module around HR.
We made a "Clausier" in a very old version of odoo (v6) for notaries and lawyers, but it would have too much effort to adapt it to the current version.
Concern your need there could be a base with agreement modules on https://github.com/OCA/contract
Have a nice day!
Bruno Joliveau - PrésidentNUMIGI SOLUTIONS INC.
(514) 317-7944
Longueuil, Québec, Canada

Le mer. 18 août 2021 à 12:22, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :
Hi OCA, A customer has a need for a solution that can allow HR users to 'build' an employee contract by selecting texts from a predefined list of HTML snippets. For example: Section A: - Clause type A (select from list) - Clause type A (select from list) - Clause type A (select from list) Section B: - Clause type B (select from list) The clauses should be poweruser-editable, translatable HTML snippets in which also placeholders can be used such as in Odoo email templates: {{employee.name}} and the like. It's possible to custom-build this, but is there anyone who has already seen something like this in action? I know some legal firms which had something like this custom-built in order to serve their customers quicker and sell them auto-generated contracts based on an online survey that the customer has to fill, thereby earning good money with very little work; but I haven't seen it in Odoo yet. -Tom_______________________________________________
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
_______________________________________________
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:05 - 19 Aug 2021 -
Re: Travis .pot push issue
Thanks for your help Stéphane!On Wed, Aug 18, 2021 at 6:52 PM Daniel Reis <dreis@opensourceintegrators.com> wrote:Five star service! Thank you Stephane. On 18/08/21 17:32, Stéphane Bidoul wrote: > Hi, > > This afternoon you may have noticed merge commands failing due to a > token error when Travis tried to push the generated .pot files back to > GitHub. > > For some reason our token had become invalid and a new one had to be > generated and pushed to the config of all repos... which was something > I had hoped to avoid since that solution was put in place. > > It is now resolved. Let me know if there are any remaining issues. > > Best regards, > > -sbi > > _______________________________________________ > 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
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 07:25 - 18 Aug 2021 -
Re: Employee contract builder in Odoo
Yes, the oca/contract "agreement" module might do what you want.
Have a look at https://github.com/OCA/contract/tree/12.0/agreement_legal
Thanks
Daniel
On 18/08/21 17:37, Bruno Joliveau wrote:
Hi Tom,
I don't remember ever having seen such a module around HR.
We made a "Clausier" in a very old version of odoo (v6) for notaries and lawyers, but it would have too much effort to adapt it to the current version.
Concern your need there could be a base with agreement modules on https://github.com/OCA/contract
Have a nice day!
Bruno Joliveau - PrésidentNUMIGI SOLUTIONS INC.
(514) 317-7944
Longueuil, Québec, Canada

Le mer. 18 août 2021 à 12:22, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :
Hi OCA, A customer has a need for a solution that can allow HR users to 'build' an employee contract by selecting texts from a predefined list of HTML snippets. For example: Section A: - Clause type A (select from list) - Clause type A (select from list) - Clause type A (select from list) Section B: - Clause type B (select from list) The clauses should be poweruser-editable, translatable HTML snippets in which also placeholders can be used such as in Odoo email templates: {{employee.name}} and the like. It's possible to custom-build this, but is there anyone who has already seen something like this in action? I know some legal firms which had something like this custom-built in order to serve their customers quicker and sell them auto-generated contracts based on an online survey that the customer has to fill, thereby earning good money with very little work; but I haven't seen it in Odoo yet. -Tom_______________________________________________
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 Daniel Reis - 06:56 - 18 Aug 2021 -
Re: Travis .pot push issue
Five star service! Thank you Stephane. On 18/08/21 17:32, Stéphane Bidoul wrote: > Hi, > > This afternoon you may have noticed merge commands failing due to a > token error when Travis tried to push the generated .pot files back to > GitHub. > > For some reason our token had become invalid and a new one had to be > generated and pushed to the config of all repos... which was something > I had hoped to avoid since that solution was put in place. > > It is now resolved. Let me know if there are any remaining issues. > > Best regards, > > -sbi > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe >
by Daniel Reis - 06:50 - 18 Aug 2021 -
Re: Travis .pot push issue
Thanks for doing the nasty maintenance work.Regards.El mié., 18 ago. 2021 18:32, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:Hi,This afternoon you may have noticed merge commands failing due to a token error when Travis tried to push the generated .pot files back to GitHub.For some reason our token had become invalid and a new one had to be generated and pushed to the config of all repos... which was something I had hoped to avoid since that solution was put in place.It is now resolved. Let me know if there are any remaining issues.Best regards,-sbi_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Pedro M. Baeza - 06:45 - 18 Aug 2021