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: Discover the OCA priorities for 2021 proposed by the board
PS. Instead of blogs, which are perhaps a bit flighty and lose their actuality value over time, it could also be some kind of permanent wiki or github-based website, which is updated and community-reviewed as time goes by, with the latest insights per functional topic and Odoo version.
Anyway, ideas ideas... good luck in the new board for 2021!
Op 3/17/21 om 10:38 AM schreef Tom Blauwendraat:
Hi Virginie
In the post you are mentioning people to react below the blog post, but I can't... so then here:
As a part of communication - maybe a method can be to make a platform that facilitates functional people to write attractive documentation/blogs/howto's about solving Odoo problems with OCA modules. For one, this could supplement the thorough lack of documentation on Odoo CE; but also, if consultants and clients read these blogs with examples and understand better that OCA modules are better than alternatives, because they:
- usually solve problems in the best way, as there is hard-won community consensus on their design
- are designed to interoperate together as a holistic eco-system
- are extendible (even better than most Odoo modules are)
- are quality-controlled
- are OpenUpgradable
- etc.
Then they would understand better why it can be commercially more interesting to choose OCA modules and avoid technical debt, then go for the latest and greatest Odoo version supported by some crude customizations and App Store modules, and become disappointed in Odoo in the long run. And then, they would also become motivated to financially support OCA.
A case in point is for example the import/export modules in the "queue" repository - I'm seeing so many inferior hand-rolled syncing implementations lately, that I'm very motivated to write a furious blog to tell everyone to stop doing that and build on the OCA solution. But now, aside from starting my own blog on the subject, I wouldn't know where to place such an article.
Tom
Op 3/17/21 om 10:12 AM schreef Virginie Dewulf:
Hello contributors,
Here is our latest blog post to present the 2021 OCA priorities proposed by the Board:
Don't hesitate to come back to us/me if you'd like to give your feedback!
Have a nice day,--
Virginie for the Board_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 10:46 - 17 Mar 2021 -
Re: Discover the OCA priorities for 2021 proposed by the board
Excellent ! Thanks for the communication efforts sharing targets and roadmaps !Le mer. 17 mars 2021 à 10:12, Virginie Dewulf <virginie@coopiteasy.be> a écrit :Hello contributors,Here is our latest blog post to present the 2021 OCA priorities proposed by the Board:Don't hesitate to come back to us/me if you'd like to give your feedback!Have a nice day,--
Virginie for the Board_______________________________________________
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 - 10:46 - 17 Mar 2021 -
Re: Discover the OCA priorities for 2021 proposed by the board
Hi Virginie
In the post you are mentioning people to react below the blog post, but I can't... so then here:
As a part of communication - maybe a method can be to make a platform that facilitates functional people to write attractive documentation/blogs/howto's about solving Odoo problems with OCA modules. For one, this could supplement the thorough lack of documentation on Odoo CE; but also, if consultants and clients read these blogs with examples and understand better that OCA modules are better than alternatives, because they:
- usually solve problems in the best way, as there is hard-won community consensus on their design
- are designed to interoperate together as a holistic eco-system
- are extendible (even better than most Odoo modules are)
- are quality-controlled
- are OpenUpgradable
- etc.
Then they would understand better why it can be commercially more interesting to choose OCA modules and avoid technical debt, then go for the latest and greatest Odoo version supported by some crude customizations and App Store modules, and become disappointed in Odoo in the long run. And then, they would also become motivated to financially support OCA.
A case in point is for example the import/export modules in the "queue" repository - I'm seeing so many inferior hand-rolled syncing implementations lately, that I'm very motivated to write a furious blog to tell everyone to stop doing that and build on the OCA solution. But now, aside from starting my own blog on the subject, I wouldn't know where to place such an article.
Tom
Op 3/17/21 om 10:12 AM schreef Virginie Dewulf:
Hello contributors,
Here is our latest blog post to present the 2021 OCA priorities proposed by the Board:
Don't hesitate to come back to us/me if you'd like to give your feedback!
Have a nice day,--
Virginie for the Board_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 10:41 - 17 Mar 2021 -
Discover the OCA priorities for 2021 proposed by the board
Hello contributors,Here is our latest blog post to present the 2021 OCA priorities proposed by the Board:Don't hesitate to come back to us/me if you'd like to give your feedback!Have a nice day,--
Virginie for the Board
by Virginie Dewulf. - 10:11 - 17 Mar 2021 -
Re: Track sales packaging costs
This trouble looks like delivery cost of Intrastat.
On intrastat statement, all delivery costs (required) and packaging costs (optional) have to be shared in COGS.
Example:
Sale Order
Product Qty Unit Price Subtotal Delivery cost Intrastat value Pack.Cost Prod.A 10,0 € 10,50 € 105,00 € 6,56 € 111,56 € 3,28 Prod.B 10,0 € 5,50 € 55,00 € 3,44 € 58,44 € 1,72 Packaging 1,0 € 5,00 € 5,00
Delivery 1,0 € 10,00 € 10,00
TOTAL
€ 175,00
Tot.Goods & Service 20
€ 160,00 € 10,00 € 170,00 € 5,00
Il 15/03/21 01:56, Marco Marchiori ha scritto:
Graeme
as you said I was not so accurate to include the IAS compliance in the discussion.
In any case we defined the nature of such costs: they are variable costs, they should be included in cogs but they could be allocated, with a sort of ABC, "depending on the sales order composition".
If they are "extra-amounts" (as Daniel said) they should be allocated in addition to the cost (apparently) already included in the product, but of course I would not discuss IAS compliance here!
So I suggested to track them separately (we agree on that).
Then the entry I advised to make was an absorption one, that would work both in continental and anglo-saxon accounting.
If I worked for a business like that (independently from IAS) I would ask myself if it's more important the cost of the product or the cost of the order...
Ciao
Marco
Il giorno dom 14 mar 2021 alle ore 21:57 Graeme Gellatly <gdgellatly@gmail.com> ha scritto:
Hi,
Under IAS2 this advice is not correct. It is very clear that product costs relate to bringing the product to its present location and condition. It cannot include non incurred costs, or costs that form part of the sales process. Now if it forms part of a manufacturing process, then they can be included under costs of conversion, but only if they are part of that conversion. If there is no production process then no costs. If there is then actually the manufacturing process handles it all already because it occurs prior to the sales transaction.
Here is the exact clause.
The cost of inventories shall comprise all costs of purchase, costs of conversion and other costs incurred in bringing the inventories to their present location and condition.
So in this case where the packaging costs are part of the sales process they do not form cost of inventories. Indeed any costs incurred in the selling process are explicitly excluded.
However it should of course be included in Cost of Goods sold, but it is no different to any other cost / revenue required at time of sale (or purchase for that matter), such as rebates, discounts on either the vendor/customer side related to a particular customer. It is a very common use case, and its the same reason you need to accrue warranty liability accrual at time of sale rather than in inventories (or time of claim for that matter). The only tricky part being the management of the sales transaction because you need some way to record that (y), which is variable in this case, but effectively you end up with.
CR Inventory - Product A x
CR Packaging y
DR COGS - Product A (x+y).
Is how I'd do it, probably just adding the packaging to the picking (not the sale) and then overriding the anglosaxon entries to allocate costs.
That is the simple case, Obviously there is a mix of products involved, all utilising the packaging, so a reasonable allocation decision needs to be made, probably a dollar weighted basis, but possibly volume. Under anglo saxon the way Odoo operates it will be a significant amount of work, as you then need to reconcile both sides of the accrual accounts, but really it is no different to the same issue you have with A/P accrual accounts and having to allow for expected rebates.
On Mon, Mar 15, 2021 at 8:32 AM Marco Marchiori <info@marcomarchiori.com> wrote:
In general (accountant's view)
1- A standard, or minimum or what-you-want package cost should be included in product cost, and "absorbed" when you FG is produced
2- The actual cost should be recorded when incurred (order > invoice)
3- The extra-package cost would be the "algebraic sum" of cost incurred and absorbed
4- The total package cost would be the sum of extra and COGS-included package cost or (sould be the same) the total cost incurred referred to the product sold
Ciao
Marco_______________________________________________
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
--
M a r c o M a r c h i o r iconsulente funzionaledottore commercialista, revisore legale
Via Stazione 12, 30035 MIRANO (VE); telefono e fax 041 488195
codice fiscale MRCMRC67H11F241M; partita IVA 03813290271
--
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. Use of such information is exclusively reserved for the recipient of this e-mail.
--
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Antonio M. Vigliotti - 10:00 - 15 Mar 2021 -
Re: Track sales packaging costs
Graeme
as you said I was not so accurate to include the IAS compliance in the discussion.
In any case we defined the nature of such costs: they are variable costs, they should be included in cogs but they could be allocated, with a sort of ABC, "depending on the sales order composition".
If they are "extra-amounts" (as Daniel said) they should be allocated in addition to the cost (apparently) already included in the product, but of course I would not discuss IAS compliance here!
So I suggested to track them separately (we agree on that).
Then the entry I advised to make was an absorption one, that would work both in continental and anglo-saxon accounting.
If I worked for a business like that (independently from IAS) I would ask myself if it's more important the cost of the product or the cost of the order...
Ciao
MarcoIl giorno dom 14 mar 2021 alle ore 21:57 Graeme Gellatly <gdgellatly@gmail.com> ha scritto:Hi,Under IAS2 this advice is not correct. It is very clear that product costs relate to bringing the product to its present location and condition. It cannot include non incurred costs, or costs that form part of the sales process. Now if it forms part of a manufacturing process, then they can be included under costs of conversion, but only if they are part of that conversion. If there is no production process then no costs. If there is then actually the manufacturing process handles it all already because it occurs prior to the sales transaction.
Here is the exact clause.
The cost of inventories shall comprise all costs of purchase, costs of conversion and other costs incurred in bringing the inventories to their present location and condition.
So in this case where the packaging costs are part of the sales process they do not form cost of inventories. Indeed any costs incurred in the selling process are explicitly excluded.
However it should of course be included in Cost of Goods sold, but it is no different to any other cost / revenue required at time of sale (or purchase for that matter), such as rebates, discounts on either the vendor/customer side related to a particular customer. It is a very common use case, and its the same reason you need to accrue warranty liability accrual at time of sale rather than in inventories (or time of claim for that matter). The only tricky part being the management of the sales transaction because you need some way to record that (y), which is variable in this case, but effectively you end up with.
CR Inventory - Product A x
CR Packaging yDR COGS - Product A (x+y).Is how I'd do it, probably just adding the packaging to the picking (not the sale) and then overriding the anglosaxon entries to allocate costs.
That is the simple case, Obviously there is a mix of products involved, all utilising the packaging, so a reasonable allocation decision needs to be made, probably a dollar weighted basis, but possibly volume. Under anglo saxon the way Odoo operates it will be a significant amount of work, as you then need to reconcile both sides of the accrual accounts, but really it is no different to the same issue you have with A/P accrual accounts and having to allow for expected rebates.On Mon, Mar 15, 2021 at 8:32 AM Marco Marchiori <info@marcomarchiori.com> wrote:
In general (accountant's view)
1- A standard, or minimum or what-you-want package cost should be included in product cost, and "absorbed" when you FG is produced
2- The actual cost should be recorded when incurred (order > invoice)
3- The extra-package cost would be the "algebraic sum" of cost incurred and absorbed
4- The total package cost would be the sum of extra and COGS-included package cost or (sould be the same) the total cost incurred referred to the product sold
Ciao
Marco_______________________________________________
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
--M a r c o M a r c h i o r iconsulente funzionaledottore commercialista, revisore legale
Via Stazione 12, 30035 MIRANO (VE); telefono e fax 041 488195
codice fiscale MRCMRC67H11F241M; partita IVA 03813290271
--
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. Use of such information is exclusively reserved for the recipient of this e-mail.
--
by Marco Marchiori - 01:56 - 15 Mar 2021 -
Re: Track sales packaging costs
Hi,Under IAS2 this advice is not correct. It is very clear that product costs relate to bringing the product to its present location and condition. It cannot include non incurred costs, or costs that form part of the sales process. Now if it forms part of a manufacturing process, then they can be included under costs of conversion, but only if they are part of that conversion. If there is no production process then no costs. If there is then actually the manufacturing process handles it all already because it occurs prior to the sales transaction.
Here is the exact clause.
The cost of inventories shall comprise all costs of purchase, costs of conversion and other costs incurred in bringing the inventories to their present location and condition.
So in this case where the packaging costs are part of the sales process they do not form cost of inventories. Indeed any costs incurred in the selling process are explicitly excluded.
However it should of course be included in Cost of Goods sold, but it is no different to any other cost / revenue required at time of sale (or purchase for that matter), such as rebates, discounts on either the vendor/customer side related to a particular customer. It is a very common use case, and its the same reason you need to accrue warranty liability accrual at time of sale rather than in inventories (or time of claim for that matter). The only tricky part being the management of the sales transaction because you need some way to record that (y), which is variable in this case, but effectively you end up with.
CR Inventory - Product A x
CR Packaging yDR COGS - Product A (x+y).Is how I'd do it, probably just adding the packaging to the picking (not the sale) and then overriding the anglosaxon entries to allocate costs.
That is the simple case, Obviously there is a mix of products involved, all utilising the packaging, so a reasonable allocation decision needs to be made, probably a dollar weighted basis, but possibly volume. Under anglo saxon the way Odoo operates it will be a significant amount of work, as you then need to reconcile both sides of the accrual accounts, but really it is no different to the same issue you have with A/P accrual accounts and having to allow for expected rebates.On Mon, Mar 15, 2021 at 8:32 AM Marco Marchiori <info@marcomarchiori.com> wrote:
In general (accountant's view)
1- A standard, or minimum or what-you-want package cost should be included in product cost, and "absorbed" when you FG is produced
2- The actual cost should be recorded when incurred (order > invoice)
3- The extra-package cost would be the "algebraic sum" of cost incurred and absorbed
4- The total package cost would be the sum of extra and COGS-included package cost or (sould be the same) the total cost incurred referred to the product sold
Ciao
Marco_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Graeme Gellatly - 09:55 - 14 Mar 2021 -
Re: Track sales packaging costs
In general (accountant's view)
1- A standard, or minimum or what-you-want package cost should be included in product cost, and "absorbed" when you FG is produced
2- The actual cost should be recorded when incurred (order > invoice)
3- The extra-package cost would be the "algebraic sum" of cost incurred and absorbed
4- The total package cost would be the sum of extra and COGS-included package cost or (sould be the same) the total cost incurred referred to the product sold
Ciao
Marco
by Marco Marchiori - 08:30 - 14 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
Il giorno mar 2 mar 2021 alle ore 12:16 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
by Francesco Apruzzese - 12:40 - 13 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
In my local instance files .pot are ok!Travis is green now here https://github.com/OCA/l10n-italy/pull/2168Il giorno ven 12 mar 2021 alle ore 16:52 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:Use the language exporter for new language and select the module :It will generate a pot file.Or use the (excellent) click-odoo-makepot ;-) https://github.com/acsone/click-odoo-contrib#click-odoo-makepot-stable--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
by Francesco Apruzzese - 05:16 - 12 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
Use the language exporter for new language and select the module :It will generate a pot file.Or use the (excellent) click-odoo-makepot ;-) https://github.com/acsone/click-odoo-contrib#click-odoo-makepot-stableOn Fri, Mar 12, 2021 at 4:17 PM Francesco Apruzzese <cescoap@gmail.com> wrote:How can I test it?Il giorno ven 12 mar 2021 alle ore 15:52 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:Great.Did you test the pot generation to check if fields are removed?Le ven. 12 mars 2021 à 15:47, Francesco Apruzzese <cescoap@gmail.com> a écrit :@Denis RousselIf I remove account_financial_report_abstract inherit, it works, too.FYI https://github.com/OCA/l10n-italy/pull/2168Il giorno ven 12 mar 2021 alle ore 13:07 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:Mmmmh, the problem is maybe there : https://github.com/OCA/l10n-italy/blob/11.0/l10n_it_account_balance_report/report/account_balance_report.py#L18The final report is inheriting several times from the same model.report_trial_balance is already inheriting from account_financial_report_abstractIs that wanted ?On Fri, Mar 12, 2021 at 12:52 PM Francesco Apruzzese <cescoap@gmail.com> wrote:How is it possible that an already merged PR gives these problems?Revert 11.0 it's the last step. I prefer to search another approach, if it's possibile.Il giorno gio 11 mar 2021 alle ore 15:42 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:That module has been merged by hand:It is causing a lot of travis jobs and commits !Could you do something about it (Revert and fixing should be a good first approach)?On Thu, Mar 11, 2021 at 3:27 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:I'd try running travis on python 3.6. IIRC python started preserving dict insertion order with that version, and that may help making Odoo's pot export deterministic.-sbiOn Thu, Mar 11, 2021 at 2:57 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Now, we have this situation:
https://github.com/OCA/l10n-italy/commits/11.0-ocabot-merge-pr-2160-by-eLBati-bump-nobumpIl giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
by Denis Roussel - 04:51 - 12 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
How can I test it?Il giorno ven 12 mar 2021 alle ore 15:52 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:Great.Did you test the pot generation to check if fields are removed?Le ven. 12 mars 2021 à 15:47, Francesco Apruzzese <cescoap@gmail.com> a écrit :@Denis RousselIf I remove account_financial_report_abstract inherit, it works, too.FYI https://github.com/OCA/l10n-italy/pull/2168Il giorno ven 12 mar 2021 alle ore 13:07 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:Mmmmh, the problem is maybe there : https://github.com/OCA/l10n-italy/blob/11.0/l10n_it_account_balance_report/report/account_balance_report.py#L18The final report is inheriting several times from the same model.report_trial_balance is already inheriting from account_financial_report_abstractIs that wanted ?On Fri, Mar 12, 2021 at 12:52 PM Francesco Apruzzese <cescoap@gmail.com> wrote:How is it possible that an already merged PR gives these problems?Revert 11.0 it's the last step. I prefer to search another approach, if it's possibile.Il giorno gio 11 mar 2021 alle ore 15:42 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:That module has been merged by hand:It is causing a lot of travis jobs and commits !Could you do something about it (Revert and fixing should be a good first approach)?On Thu, Mar 11, 2021 at 3:27 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:I'd try running travis on python 3.6. IIRC python started preserving dict insertion order with that version, and that may help making Odoo's pot export deterministic.-sbiOn Thu, Mar 11, 2021 at 2:57 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Now, we have this situation:
https://github.com/OCA/l10n-italy/commits/11.0-ocabot-merge-pr-2160-by-eLBati-bump-nobumpIl giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
by Francesco Apruzzese - 04:16 - 12 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
Great.Did you test the pot generation to check if fields are removed?Le ven. 12 mars 2021 à 15:47, Francesco Apruzzese <cescoap@gmail.com> a écrit :@Denis RousselIf I remove account_financial_report_abstract inherit, it works, too.FYI https://github.com/OCA/l10n-italy/pull/2168Il giorno ven 12 mar 2021 alle ore 13:07 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:Mmmmh, the problem is maybe there : https://github.com/OCA/l10n-italy/blob/11.0/l10n_it_account_balance_report/report/account_balance_report.py#L18The final report is inheriting several times from the same model.report_trial_balance is already inheriting from account_financial_report_abstractIs that wanted ?On Fri, Mar 12, 2021 at 12:52 PM Francesco Apruzzese <cescoap@gmail.com> wrote:How is it possible that an already merged PR gives these problems?Revert 11.0 it's the last step. I prefer to search another approach, if it's possibile.Il giorno gio 11 mar 2021 alle ore 15:42 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:That module has been merged by hand:It is causing a lot of travis jobs and commits !Could you do something about it (Revert and fixing should be a good first approach)?On Thu, Mar 11, 2021 at 3:27 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:I'd try running travis on python 3.6. IIRC python started preserving dict insertion order with that version, and that may help making Odoo's pot export deterministic.-sbiOn Thu, Mar 11, 2021 at 2:57 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Now, we have this situation:
https://github.com/OCA/l10n-italy/commits/11.0-ocabot-merge-pr-2160-by-eLBati-bump-nobumpIl giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Denis Roussel - 03:51 - 12 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
@Denis RousselIf I remove account_financial_report_abstract inherit, it works, too.FYI https://github.com/OCA/l10n-italy/pull/2168Il giorno ven 12 mar 2021 alle ore 13:07 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:Mmmmh, the problem is maybe there : https://github.com/OCA/l10n-italy/blob/11.0/l10n_it_account_balance_report/report/account_balance_report.py#L18The final report is inheriting several times from the same model.report_trial_balance is already inheriting from account_financial_report_abstractIs that wanted ?On Fri, Mar 12, 2021 at 12:52 PM Francesco Apruzzese <cescoap@gmail.com> wrote:How is it possible that an already merged PR gives these problems?Revert 11.0 it's the last step. I prefer to search another approach, if it's possibile.Il giorno gio 11 mar 2021 alle ore 15:42 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:That module has been merged by hand:It is causing a lot of travis jobs and commits !Could you do something about it (Revert and fixing should be a good first approach)?On Thu, Mar 11, 2021 at 3:27 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:I'd try running travis on python 3.6. IIRC python started preserving dict insertion order with that version, and that may help making Odoo's pot export deterministic.-sbiOn Thu, Mar 11, 2021 at 2:57 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Now, we have this situation:
https://github.com/OCA/l10n-italy/commits/11.0-ocabot-merge-pr-2160-by-eLBati-bump-nobumpIl giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
by Francesco Apruzzese - 03:46 - 12 Mar 2021 -
Re: Password manager within Odoo
Thank you very much for the feedback. I'll go with this suggestion because password_security might be useful in the future. https://github.com/OCA/server-auth/pull/254 Am 23.02.21 um 13:37 schrieb Pedro M. Baeza (Tecnativa): > Maybe server-auth? > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Mit freundlichen Grüßen Florian Kantelberg Softwareentwickler initOS GmbH An der Eisenbahn 1 21224 Rosengarten Tel.: +49 (0) 4105 5615644 Fax: +49 (0) 4105 5615610 Email: florian.kantelberg@initos.com Internet: http://www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht: Tostedt, HRB 205226 USt-IdNr: DE 815580155 Steuer-Nr: 15/200/53247
by Florian Kantelberg - 02:16 - 12 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
Mmmmh, the problem is maybe there : https://github.com/OCA/l10n-italy/blob/11.0/l10n_it_account_balance_report/report/account_balance_report.py#L18The final report is inheriting several times from the same model.report_trial_balance is already inheriting from account_financial_report_abstractIs that wanted ?On Fri, Mar 12, 2021 at 12:52 PM Francesco Apruzzese <cescoap@gmail.com> wrote:How is it possible that an already merged PR gives these problems?Revert 11.0 it's the last step. I prefer to search another approach, if it's possibile.Il giorno gio 11 mar 2021 alle ore 15:42 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:That module has been merged by hand:It is causing a lot of travis jobs and commits !Could you do something about it (Revert and fixing should be a good first approach)?On Thu, Mar 11, 2021 at 3:27 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:I'd try running travis on python 3.6. IIRC python started preserving dict insertion order with that version, and that may help making Odoo's pot export deterministic.-sbiOn Thu, Mar 11, 2021 at 2:57 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Now, we have this situation:
https://github.com/OCA/l10n-italy/commits/11.0-ocabot-merge-pr-2160-by-eLBati-bump-nobumpIl giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
by Denis Roussel - 01:05 - 12 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
How is it possible that an already merged PR gives these problems?Revert 11.0 it's the last step. I prefer to search another approach, if it's possibile.Il giorno gio 11 mar 2021 alle ore 15:42 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:That module has been merged by hand:It is causing a lot of travis jobs and commits !Could you do something about it (Revert and fixing should be a good first approach)?On Thu, Mar 11, 2021 at 3:27 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:I'd try running travis on python 3.6. IIRC python started preserving dict insertion order with that version, and that may help making Odoo's pot export deterministic.-sbiOn Thu, Mar 11, 2021 at 2:57 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Now, we have this situation:
https://github.com/OCA/l10n-italy/commits/11.0-ocabot-merge-pr-2160-by-eLBati-bump-nobumpIl giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
by Francesco Apruzzese - 12:51 - 12 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
That module has been merged by hand:It is causing a lot of travis jobs and commits !Could you do something about it (Revert and fixing should be a good first approach)?On Thu, Mar 11, 2021 at 3:27 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:I'd try running travis on python 3.6. IIRC python started preserving dict insertion order with that version, and that may help making Odoo's pot export deterministic.-sbiOn Thu, Mar 11, 2021 at 2:57 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Now, we have this situation:
https://github.com/OCA/l10n-italy/commits/11.0-ocabot-merge-pr-2160-by-eLBati-bump-nobumpIl giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
by Denis Roussel - 03:41 - 11 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
Regarding commits generated by makepot, the reference id generated ("account_balance_report" concatenated with <field name>) for the three fields with _<number> is not unique (that's why they have a different id at each try).I already have such issue on a former project.Could you try changing those fields names ?On Thu, Mar 11, 2021 at 2:57 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Now, we have this situation:
https://github.com/OCA/l10n-italy/commits/11.0-ocabot-merge-pr-2160-by-eLBati-bump-nobumpIl giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
by Denis Roussel - 03:26 - 11 Mar 2021 -
Re: OCA BOT can't merge PRs in OCA/l10n-italy branch 11.0
I'd try running travis on python 3.6. IIRC python started preserving dict insertion order with that version, and that may help making Odoo's pot export deterministic.-sbiOn Thu, Mar 11, 2021 at 2:57 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Now, we have this situation:
https://github.com/OCA/l10n-italy/commits/11.0-ocabot-merge-pr-2160-by-eLBati-bump-nobumpIl giorno mar 2 mar 2021 alle ore 15:12 Lorenzo Battistini <elbaddy@gmail.com> ha scritto:So, the best thing to do is to fix https://github.com/OCA/l10n-italy/issues/1921On Tue, 2 Mar 2021 at 12:16, Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:The test failure looks real although it does not appear with each run.Regarding the pot file not stabilizing I'm not sure what to do. Maybe trying with python 3.6 ?-sbiOn Tue, Mar 2, 2021 at 11:27 AM Francesco Apruzzese <cescoap@gmail.com> wrote:Hi Stéphane.Is there anything we need to do in our repo?Il giorno lun 1 mar 2021 alle ore 17:52 Stéphane Bidoul <stephane.bidoul@acsone.eu> ha scritto:Hi Francesco,For the second one, the error can be seen on the last commit here:So it seems to be a real test error, but one that does not appear during all builds.Also, it seems that Odoo's .pot file exporter has difficulties producing a stable result, with several commits updating the same .pot file.I'd suggest first trying to understand the test failure, then we can see if the pot file issue needs addressing (maybe by upgrading to python 3.6).-sbiOn Mon, Mar 1, 2021 at 2:21 PM Francesco Apruzzese <cescoap@gmail.com> wrote:Can anyone help us to understand why the BOT can't merge this PRor this one?Thank you.--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
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
--Lorenzo Battistini
https://github.com/eLBati_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Francesco ApruzzeseProfilo professionale: http://it.linkedin.com/in/francescoapruzzese
Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.
Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 03:26 - 11 Mar 2021