Archives
Contributors
-
Re: pre-commit help
Not all the errors that precommit gives are automatically solved, some you have to solve them manually.
Usually the precommit log as displayed on the PR is pretty clear about what the problem is.
14 aug. 2024 23:01:57 Matt Taylor <notifications@odoo-community.org>:
I'm having trouble with pre-commit. Can someone give me a few tips?
I tried to follow the instructions in the README for maintainer-tools:
I installed maintainer-tools and activated the venv, then ran the following
.../repo/module$ pre-commit run --all-files --show-diff-on-failure --color=always
Still failing the pre-commit test on pull request.
Maybe there is more documentation that I am missing?
Matt
_______________________________________________
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 - 08:31 - 15 Aug 2024 -
-
Re: pre-commit help
To run pre-commit, you first need to install it:
$ pip install pre-commit
And then in (each) cloned repo, install the pre-commit hooks with:
$ pre-commit install
Now you can run :
$ pre-commit run -a
At least that's what works for me.
--Daniel
On 14/08/2024 22:01, Matt Taylor wrote:
I'm having trouble with pre-commit. Can someone give me a few tips?
I tried to follow the instructions in the README for maintainer-tools:
I installed maintainer-tools and activated the venv, then ran the following
.../repo/module$ pre-commit run --all-files --show-diff-on-failure --color=always
Still failing the pre-commit test on pull request.
Maybe there is more documentation that I am missing?
Matt
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
DANIEL REIS
MANAGING PARTNERMeet with me.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais![[Logo OpenSourceIntegrators.com]](https://www.opensourceintegrators.com/images/opensource-logo-2022.svg)
by Daniel Reis - 11:22 - 14 Aug 2024 -
pre-commit help
I'm having trouble with pre-commit. Can someone give me a few tips?I tried to follow the instructions in the README for maintainer-tools:I installed maintainer-tools and activated the venv, then ran the following.../repo/module$ pre-commit run --all-files --show-diff-on-failure --color=alwaysStill failing the pre-commit test on pull request.Maybe there is more documentation that I am missing?Matt
by Matt - 11:00 - 14 Aug 2024 -
Re: Overtime calculation in Odoo 15 and OCA
Hello Akim, hello all!After one year, did you finally take this solution for Odoo 16? I'm curious as we are near Odoo 18 and nobody review o migrates this Odoo 15 solutions to Odoo 16 one year before.As a resume:1. Odoo FIX several things:
- [FIX] hr(_contract)(_attendance): Make overtime computation contract-based #159477 https://github.com/odoo/odoo/pull/159477
- [FIX] hr(_contract)(_attendance): Make overtime computation contract-based #59539 https://github.com/odoo/enterprise/pull/59539
- [FIX] hr_attendance: Allow contract based overtime computation #168839 https://github.com/odoo/odoo/pull/1688392. Florian develop 3 modules- hr_attendance_missing_days- Merged in 15: https://github.com/OCA/hr-attendance/pull/140
- Open PR in 16: https://github.com/OCA/hr-attendance/pull/165- hr_attendance_overtime_manual- Merged in 15: https://github.com/OCA/hr-attendance/pull/141
- Open PR in 16: https://github.com/OCA/hr-attendance/pull/166- hr_holidays_type_visibility- Open PR in 15: https://github.com/OCA/hr-holidays/pull/86- No migration to 16It seems that the OCA solution is not widely used by everyone.Thank you for your feedback.Best regards,RafaelEl mié, 18 oct 2023 a las 17:02, Akim Juillerat (<notifications@odoo-community.org>) escribió:HelloI'm a bit late on the topic but was pleasantly surprised to see some other people in the OCA having worked on these issues.Going through all the exchanges here, my feeling is that https://github.com/OCA/hr-attendance/pull/140 and https://github.com/OCA/hr-holidays/pull/87 can a go a long way in solving the core issues from Odoo standard.However, as we are working on a v16.0 project, did anyone already spend time on migrating these modules?We might do it if the testing in v15 matches our client's request, but I prefer to ask before starting.Anyway, huge thanks to all the contributors for the good job.camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSAkim JuilleratBusiness solutionsSoftware architectOn Thu, Aug 10, 2023 at 2:31 PM Florian Kantelberg <notifications@odoo-community.org> wrote:Hello,
as promised I want to provide links to the PRs we created so far.
- https://github.com/odoo/odoo/pull/131558
- This is a core patch to use the resource calendar provided by the hr.contract if the module is also installed to calculate the overtime (hr.attendance.overtime)
- https://github.com/OCA/hr-attendance/pull/140
- This is a module which generates the missing pseudo attendances (with hr.attendance.reason) for working days without attendances
- I already saw that Holger pushed something similar as draft but in the PR is also code which overwrites other places not everyone might want. Also our testing took a bit longer. I hope this isn't a problem for you Holger?
- https://github.com/OCA/hr-attendance/pull/141
- hr_attendance_overtime_manual
- Small gimmick which will be used for our migration between systems to set the initial offsets. We also have other edge cases where this might be useful.
- https://github.com/OCA/hr-holidays/pull/86
- hr_holidays_type_visibility
- Another annoyance was that Odoo hides leave types with a virtual_remaining_leaves <= 0 automatically. To have an even better overview for the employee we made the visibility configurable.
We would appreciate feedback or if you find bugs. We generally intend to make the Odoo standard models work here to get the most value out of it.
Best Regards,
Florian
Am 10.08.23 um 11:41 schrieb Stefan Wild | sewisoft.de:
Hi Frederik,
I get you point of course. What I can add here is, that there is a boolean flag in the attendance record, where you see that it is generated.
So for that, you are able every time to delete all generated records, if you want. (Perhaps to that time, that Odoo fixes the problem ;-)
I think to build a working patch, needs a lot of refactoring, because everything of overtime calculation is based on attendance records.
And the only way to consider them is, when they really exist.
I also would be more happy, if it wouldn't need such a workaround.
Anyway, this solution fits to our needs, and I just want to share it with all of you. No force to use it.
Vielen Dank und viele Grüße
Stefan Wild
Geschäftsführersewisoft GmbH
Örtleinsweg 39
96148 Baunach
info@sewisoft.de
Tel. +49 (0) 160 / 99 11 25 69
www.sewisoft.deSitz der Gesellschaft: Baunach
Registergericht: Amtsgericht Bamberg, HRB 8508
Geschäftsführer: Günter Selbert, Stefan Wild
Am 10.08.23 um 09:17 schrieb Frederik Kramer:
Hi Stefan,
grounding your work on Odoo Standard is what we usually do as well, as it limits the upstream work and even more importantly the maintenance effort. However, i am genuinly not a friend of "dirty" work arounds like the one you described, even if that is definitely pragmatic. The reason is simple: Attendance of 0 effectively means, a given employee was attending but technically less than the minimum recordable time. So if the authorities see that record at a given time in the future, they might be tempted to belive there was an error with regard to the recorded time. Moreover an attendenance cron job means, the entry has not been made by the employee or a manager (human), which mit might not be favourable either (with regard to law and credibility of the system).
Overall i believe, your strategy is pragmatic but less favourable from a legal standpoint.
So why not patching the standard functionality, so that it calculates "0" when there is no entry and sent this patch for upstream inclusion? I know this is generally a bumpy road with Odoo but to me that would be the best solution for the given problem
Best Frederik
Am 09.08.23 um 23:52 schrieb Stefan Wild | sewisoft.de:
Hello everyone,
I pained about the same issues, you are all telling about. I just can speak for version 16. Probably 15 too, but I‘am not sure. Our module depends to Odoo Core only.
Our biggest pain was, that the overtime is not reduced on days without attendance, where you normally have to work.
For that problem we found a really simple solution.The approach was, when you have attendances, then overtime calculation is correct.The trick is, we create an attendance with zero time for days, where no attendance entries exist.
Therefore we have implemented a cronjob which runs every night and creates missing attendances for days where are no entries. We use here the „generate_series“ method from postgres.
You also have got a new field „count_attendance_from“ in employee. Starting from that date, all missing attendances are generated with zero time.
If anyone is interested, here is a link to the code.I just uploaded it to github, while primarily we are using gitlab.
In this repository there are two more modules. Once for generating public holidays worldwide using pythons holiday library and one module, for updating overtime when creating the holidays later.
hr_attendance_no_gaps:Module for correct overtime calculation
hr_generate_public_holidays:Module for generating holidays
hr_holidays_attendance_overtime:Bridge module between hr_attendance and hr_holidays to update overtime.
We also would contribute them to oca, but haven‘t written any tests yet. Feel free to contribute :)
Vielen Dank und Viele Grüße
Stefan Wild
Geschäftsführer
sewisoft GmbH
Örtleinsweg 39
96148 Baunach
info@sewisoft.de
Tel. +49 (0) 160 / 99 11 25 69
www.sewisoft.deSitz der Gesellschaft: Baunach
Registergericht: Amtsgericht Bamberg, HRB 8508
Geschäftsführer: Günter Selbert, Stefan Wild
Am 08.08.2023 um 15:11 schrieb Rafael Blasco <notifications@odoo-community.org>:
Hello Florian, Holger:
After testing and testing in runbot I don’t catch up the “issue” for me is working properly.
I will try to test the OCA PR to get in a defined user cases (we can write down) the difference.
Regards
Rafael
De: Holger Brunn <notifications@odoo-community.org>
Enviado el: martes, 8 de agosto de 2023 7:42
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Overtime calculation in Odoo 15 and OCA> Is your proposal to transfer times from time-sheet / attendance -> payslip> CODE according to some rules (like the Salary Rules). I am running older> version of Odoo and upgrading to 16 ATM and would like to incorporate a> feature like this.no, it might be built on top of my proposal though. I'm now exclusivelytalking about populating hr.attendance.overtime in a way thatovertime = (time recorded in hr.attendance records) - (expected working hoursas per working calendar)holds--Your partner for the hard Odoo problemshttps://hunki-enterprises.com
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel: +49 (0) 4181 13503 12 Fax: +49 (0) 4181 13503 10 Mobil: +49 (0) 179 3901819 Email: frederik.kramer@initos.com Internet: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 USt-IdNr.: DE815580155 Steuer-Nr: 15/200/53247
_______________________________________________
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
-- Mit freundlichen Grüßen Florian Kantelberg Softwareentwickler initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Tel.: +49 (0) 4181 1350344 Fax: +49 (0) 4181 1350310 Email: florian.kantelberg@initos.com Internet: https://www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht: Tostedt, HRB 205226 USt-IdNr: DE 815580155 Steuer-Nr: 15/200/53247
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rafael Blasco (Moduon) - 05:50 - 13 Aug 2024 -
Re: Highlights on my contributions to Odoo Community Association
Ok, it is really good and useful to refer to all the points that I still miss.
Some of this information is very new to me like mentioning the PR in a comment of the "Migration to version 17.0 #1446" PR.
In addition to this, I am not aware of what still missing to merge the PR, I only know that there should be two reviews, only!
But if there is still something that I do not know please help me to get it and fill the gap.
As all of that will be mentioned on the same blog post, and we all will benefit and the rest of the world.
Thanks.On Tue, Aug 13, 2024 at 5:51 PM Radovan Skolnik <notifications@odoo-community.org> wrote:Hi,
first of all thank you for your effort. New contrinutors are always welcome. We all know the learning curve is quite steep from beginning but try to help.
I did quick review of your blog post. Few suggestions:
*) Update the formatting to make it more readable. After the first paragraph the font gets quite small and colors hard to see:
*) There is no need in my opinion to repeat contents of the links that ar provided. Rather focus on things that were not so obvious (if any) from the instructions.
*) "(7) After pushing changes to your copy of the original repository on GitHub, compare your version ..." - you're describing standard PR functionality of GitHub. It would be better to say so.
*) "After that you can send an email on OCA mailing list, and you can ask if someone is ready to review your upgraded module and make testing on it." This actually is not really the way most modules are migrated - people usually do not announce their PR in mailing list. Instead they may mention (through @ in comments) the maintainer(s) of the module/repository to draw their attention.
*) One more think you could have done (and is a good practice) is mentioning your PR in the comments of "Migration to version XX.0" - in your case https://github.com/OCA/product-attribute/issues/1446
One more thing you may decide to include into your article and/or realize yourself: In your email you mention "you succeeded after a huge effort" and your "successful pull request". So far you have succeeded partially only - your PR passes required automated tests which is absolute necessity for it to be considered worth merging. You do not yet have enough approvals (you actually have none so far) and the required time limit has not been reached after that. I can't quickly find the document that describes this. Only after you gather enough (2 I think) approvals and that time limit passes the PR can be merged and considered successfull.
So I'd suggest working the additional steps till you reach the end of the process for your blog post (and first migration) to be complete.
Best luck and regards
Radovan Skolnik
On utorok 13. augusta 2024 16:17:08 CEST mohamed alkobrosly wrote:
> Here is my experience with my first contribution to OCA:
> https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo
> .html [1] I hope it will be useful to the new contributors.
> Thanks all,
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [2]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [3]
>
>
>
> [1]
> https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo
> .html [2] https://odoo-community.org/groups/contributors-15
> [3] https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Mohamed Alkobrosly - 05:11 - 13 Aug 2024 -
Re: Highlights on my contributions to Odoo Community Association
Hi,
first of all thank you for your effort. New contrinutors are always welcome. We all know the learning curve is quite steep from beginning but try to help.
I did quick review of your blog post. Few suggestions:
*) Update the formatting to make it more readable. After the first paragraph the font gets quite small and colors hard to see:
*) There is no need in my opinion to repeat contents of the links that ar provided. Rather focus on things that were not so obvious (if any) from the instructions.
*) "(7) After pushing changes to your copy of the original repository on GitHub, compare your version ..." - you're describing standard PR functionality of GitHub. It would be better to say so.
*) "After that you can send an email on OCA mailing list, and you can ask if someone is ready to review your upgraded module and make testing on it." This actually is not really the way most modules are migrated - people usually do not announce their PR in mailing list. Instead they may mention (through @ in comments) the maintainer(s) of the module/repository to draw their attention.
*) One more think you could have done (and is a good practice) is mentioning your PR in the comments of "Migration to version XX.0" - in your case https://github.com/OCA/product-attribute/issues/1446
One more thing you may decide to include into your article and/or realize yourself: In your email you mention "you succeeded after a huge effort" and your "successful pull request". So far you have succeeded partially only - your PR passes required automated tests which is absolute necessity for it to be considered worth merging. You do not yet have enough approvals (you actually have none so far) and the required time limit has not been reached after that. I can't quickly find the document that describes this. Only after you gather enough (2 I think) approvals and that time limit passes the PR can be merged and considered successfull.
So I'd suggest working the additional steps till you reach the end of the process for your blog post (and first migration) to be complete.
Best luck and regards
Radovan Skolnik
On utorok 13. augusta 2024 16:17:08 CEST mohamed alkobrosly wrote:
> Here is my experience with my first contribution to OCA:
> https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo
> .html [1] I hope it will be useful to the new contributors.
> Thanks all,
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [2]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [3]
>
>
>
> [1]
> https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo
> .html [2] https://odoo-community.org/groups/contributors-15
> [3] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 04:50 - 13 Aug 2024 -
Highlights on my contributions to Odoo Community Association
Here is my experience with my first contribution to OCA:I hope it will be useful to the new contributors.
Thanks all,
by Mohamed Alkobrosly - 04:16 - 13 Aug 2024 -
Re: upgrade "product_pricelist_fixed_currency_rate" from 16.0 to 17.0
yes, sure I will write my experience in a post on my blog and share it with you very soon
On Tue, Aug 13, 2024, 15:12 Virginie Dewulf <virginie@odoo-community.org> wrote:Hello Mohamed,Thanks for your first contribution, which was already reviewed by an OCA maintainer, I see.Please share your blog post with us once ready, it will certainly help others!Le ven. 9 août 2024 à 01:05, mohamed alkobrosly <notifications@odoo-community.org> a écrit :I may need some members to review the module and some others to translate also, thanks.On Fri, Aug 9, 2024 at 1:55 AM mohamed alkobrosly <alkobroslymohamed@gmail.com> wrote:Dear all OCA members, I am delighted to say that I have just committed my first contribution to your organization.
I succeeded after a huge effort, I was tracking the errors that prohibited me from doing the commit successfully.
I found that there is a syntax error in the code written in the documentation for upgrading from v16 to v17.
There was a dependency that I had to install manually.
But I will write about my experience in my blog hoping that it helps me in the future and anybody who needs to contribute.
Here is my successful pull request:
https://github.com/OCA/product-attribute/pull/1706
Thanks to everybody who answered my questions and thanks to you all._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Mohamed Alkobrosly - 02:16 - 13 Aug 2024 -
Re: upgrade "product_pricelist_fixed_currency_rate" from 16.0 to 17.0
Hello Mohamed,Thanks for your first contribution, which was already reviewed by an OCA maintainer, I see.Please share your blog post with us once ready, it will certainly help others!Le ven. 9 août 2024 à 01:05, mohamed alkobrosly <notifications@odoo-community.org> a écrit :I may need some members to review the module and some others to translate also, thanks.On Fri, Aug 9, 2024 at 1:55 AM mohamed alkobrosly <alkobroslymohamed@gmail.com> wrote:Dear all OCA members, I am delighted to say that I have just committed my first contribution to your organization.
I succeeded after a huge effort, I was tracking the errors that prohibited me from doing the commit successfully.
I found that there is a syntax error in the code written in the documentation for upgrading from v16 to v17.
There was a dependency that I had to install manually.
But I will write about my experience in my blog hoping that it helps me in the future and anybody who needs to contribute.
Here is my successful pull request:
https://github.com/OCA/product-attribute/pull/1706
Thanks to everybody who answered my questions and thanks to you all._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Virginie Dewulf - 02:06 - 13 Aug 2024 -
Re: Odoo Experience Exhibition 2024, Visitors Data
YES INTERESTEDCordialement, Best regards,Karim DINMAMODE
— Associé
Tél : +33 (0)7 81 51 75 24
+261 (0)34 20 780 30
Mail : karim@nexources.com
Map : 22 Rue Andrianary Ratianarivo
Immeuble ex-Teillet Labrousse
Antananarivo Madagascar
Le lun. 12 août 2024 à 17:57, Amelia <notifications@odoo-community.org> a écrit :Hope you are doing well !!
To help you, we are offering detailed visitor data collected for the exhibition
We are following up to confirm if you are interested in acquiring the Visitors/Attendees List.
Event Name : Odoo Experience Exhibition 2024
Date : 02 - 04 Oct 2024
Location : Brussels Expo - Exhibition Center, Brussels, Belgium
Counts : 4,300
If you are interested in acquiring the Exact list, we can Send you the Discounted cost and real additional details.
Each record of the list contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.
Exhibitors who utilized our visitor data in previous events have seen a significant increase in lead conversion rates and tailored their follow-up strategies effectively. By analyzing this data, you can better understand your audience, refine your marketing approach, and follow up with highly qualified leads.
We are looking forward to hearing from you.
If you interested to take visitors list, please reply to me has ” YES INTRESTED “
Thanks & Regards,
Eliza
Market Analyst.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Karim Dinmamode - 05:08 - 12 Aug 2024 -
Re: upgrade "product_pricelist_fixed_currency_rate" from 16.0 to 17.0
I may need some members to review the module and some others to translate also, thanks.On Fri, Aug 9, 2024 at 1:55 AM mohamed alkobrosly <alkobroslymohamed@gmail.com> wrote:Dear all OCA members, I am delighted to say that I have just committed my first contribution to your organization.
I succeeded after a huge effort, I was tracking the errors that prohibited me from doing the commit successfully.
I found that there is a syntax error in the code written in the documentation for upgrading from v16 to v17.
There was a dependency that I had to install manually.
But I will write about my experience in my blog hoping that it helps me in the future and anybody who needs to contribute.
Here is my successful pull request:
https://github.com/OCA/product-attribute/pull/1706
Thanks to everybody who answered my questions and thanks to you all.
by Mohamed Alkobrosly - 01:04 - 9 Aug 2024 -
upgrade "product_pricelist_fixed_currency_rate" from 16.0 to 17.0
Dear all OCA members, I am delighted to say that I have just committed my first contribution to your organization.
I succeeded after a huge effort, I was tracking the errors that prohibited me from doing the commit successfully.
I found that there is a syntax error in the code written in the documentation for upgrading from v16 to v17.
There was a dependency that I had to install manually.
But I will write about my experience in my blog hoping that it helps me in the future and anybody who needs to contribute.
Here is my successful pull request:
https://github.com/OCA/product-attribute/pull/1706
Thanks to everybody who answered my questions and thanks to you all.
by Mohamed Alkobrosly - 12:56 - 9 Aug 2024 -
OCA Volunteers Needed - Odoo Community Days India - 23-24 August.
Hello OCA Contributors.
I hope this finds you well.We have a booth at the upcoming India Odoo Community Days.We've had some awesome support from the Serpent and BizzApp teams who have volunteered to help on the stand - we are hoping we could get a few more volunteers from our community to put in an hour or two over the two days.The task at hand is to help promote the OCA within India and answer any questions people may have about the OCA.
Alternatively, if you are new to the OCA and/or want to find out more about the OCA, come and visit our stand to have a chat in person - we are at E1S33.
The great news is the event is free and open to the public! The Basic Pass gives access to Conferences, Exhibition & Talks during event days (August 23-24, 2024).Our OCA community looks forward to seeing you.Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly (OCA) - 12:10 - 9 Aug 2024 -
Readme file genetating fails
while running this command:
pre-commit run -a
to upgrade a module from v16 to v17 I got that error:
Generate addons README files from fragments..............................Failed
- hook id: oca-gen-addon-readme
- files were modified by this hook
and my name as a contributor is not added
by Mohamed Alkobrosly - 11:51 - 8 Aug 2024 -
Re: pre-commit run -a failed
You have to manually install pandoc library requirement.Regards.
by Pedro M. Baeza - 08:56 - 8 Aug 2024 -
pre-commit run -a failed
I wonder why this error arises up, and how can it be solved:
Generate addons README files from fragments..............................Failed
- hook id: oca-gen-addon-readme
- exit code: 1File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['ar', 'x', '/home/kobros/Documents/odoo/product-attribute/pandoc-3.3-1-amd64.deb']' returned non-zero exit status 1.
I hope someone help me to solve the issue to upgrade from v16 to v17
by Mohamed Alkobrosly - 08:50 - 8 Aug 2024
